domain name access method and device

专利摘要:
The present invention relates to a domain name access method and device, used to increase the communication efficiency of a terminal device. In the present solution, after implementing the resolution of a domain name requested by a terminal device, a DNS server sends the IP address of the resolved application server and the condition of use information to the terminal device. Thus, when the terminal device moves and its information changes, and the entire terminal device does not meet the conditions indicated by the condition of use information, the terminal device can reimplement the DNS resolution of the domain name. When the terminal device does not meet the conditions indicated by the usage condition information, the previously resolved application server can no longer be the most suitable application server for the terminal device. Through this solution, the terminal device will be able to redeploy the DNS resolution of the domain name and thus acquire the most appropriate applicator server. In this way, the present solution improves the communication efficiency of the terminal device and prevents the waste of transmission resources in the communication system.
公开号:BR112020008132A2
申请号:R112020008132-9
申请日:2018-09-19
公开日:2020-11-03
发明作者:Jiao YANG；Yan Li
申请人:Huawei Technologies Co., Ltd.；
IPC主号:

专利说明:

[001] [001] This application claims priority to Chinese Patent Application No. 201711025295.8, filed with the National Intellectual Property Administration of China on October 27, 2017, and entitled "DOMAIN NAME ACCESS METHOD AND DEVICE", which is hereby incorporated by reference in its entirety. TECHNICAL FIELD
[002] [002] This application concerns the field of communications technologies, and in particular, a domain name access method and device. BACKGROUND
[003] [003] A Domain Name System (DNS) is a distributed database of information about the host, and can provide mapping and translation between a domain name and an Internet Protocol ( IP)). A terminal device can obtain an IP address from a corresponding application server by resolving to a domain name to be accessed through a DNS server.
[004] [004] Currently, a process in which the terminal device accesses a destination domain name through DNS includes the following steps. The terminal device obtains the destination domain name, and then sends a domain name resolution request message leading the destination domain name to the DNS server in DNS. After receiving the domain name resolution request message, the DNS server obtains, by resolution, an IP address from a destination application server corresponding to the destination domain name, adds the IP address of the application server from destination to a domain name resolution reply message, and sends the domain name resolution reply message to the terminal device. After receiving the domain name resolution reply message, the terminal device obtains the IP address of the destination application server, and performs data transmission with the destination application server based on the address.
[005] [005] After obtaining the IP address corresponding to the domain name, the terminal device generates and temporarily stores a DNS caching record. The DNS caching record is used to represent a match between the domain name and the IP address. In addition, for each DNS caching record that is temporarily stored, the terminal device maintains a corresponding time to live (TTL). The DNS caching record TTL is a period of time during which the DNS caching record is stored in a cache on the terminal device. In this way, if the terminal device needs to access the domain name in the DNS caching record again within the TTL of the DNS caching record, the terminal device can directly obtain, based on the DNS caching record, the IP address corresponding to the domain name. If the terminal device needs to access the domain name again after the TTL of the DNS caching record, the terminal device will need to obtain, through the previous process, the IP address corresponding to the domain name through the resolution through the DNS server.
[006] [006] However, within the time period during which the DNS caching record is stored on the terminal device, the IP address corresponding to the domain name in the DNS caching record may no longer be the most suitable for the terminal device due to factors such as mobility of the terminal device and the deployment of the application server. For example, the application server to which the IP address belongs is no longer the application server that is closest to the terminal device. In this case, if the terminal device still accesses the domain name using the DNS caching record, the terminal device may access an inappropriate application server. Consequently, the relatively low communication efficiency of the terminal device and the waste of transmission resources in a communications system are caused. SUMMARY
[007] [007] This application provides a domain name access method and device to improve the communication efficiency of a terminal device.
[008] [008] According to a first aspect, one embodiment of this request provides a domain name access method. The method can include the following steps.
[009] [009] A DNS server receives, from a terminal device, a request message including a domain name, and then performs the resolution on the domain name to obtain an IP address of an application server corresponding to the domain name; and the DNS server then sends a response message to the terminal device including the IP address of the application server and the condition of use information, where the condition of use information indicates a condition in which the terminal device accesses the name domain name using the application server's IP address.
[0010] [0010] When the terminal device information is changed and the terminal device no longer satisfies the condition indicated by the usage condition information, the application server previously obtained through the resolution can no longer be the application server that is the most suitable to the terminal device. In this case, according to the method, the terminal device can obtain another suitable application server by re-executing the DNS resolution on the domain name. Therefore, in the method, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system is also avoided.
[0011] [0011] In a possible design, the condition of use information includes at least one information among the defined information and the location range information. The defined information indicates at least one IP address of the terminal device, and the location range information indicates a location range in which the terminal device is located.
[0012] [0012] According to the design, the DNS server can limit, with the use of the IP address of the terminal device and the location information of the terminal device, the condition in which the terminal device accesses the domain name using the address Application server IP.
[0013] [0013] In a possible design, the DNS server determines the condition of use information based on the request message received.
[0014] [0014] In a possible design, when the request message additionally includes the location information of the terminal device or an IP address of the terminal device, the DNS server can determine the condition of use information based on the location information of the terminal device or the IP address of the terminal device included in the request message.
[0015] [0015] According to the design, the DNS server can determine the condition of use information based on the current location information of the terminal device or the current IP address of the terminal device, so that it can be ensured that the application server be the most suitable for the terminal device when it is determined that the terminal device meets the condition indicated by the condition of use information.
[0016] [0016] In a possible design, at least one IP address indicated by the defined information includes the IP address of the terminal device; or the location range indicated by the location range information includes a location indicated by the location information of the terminal device. In this way, it can be ensured that when accessing the domain name again when there is no change in the IP address of the terminal device or in the location of the terminal device, the terminal device can directly access the domain name using the IP address of the application server obtained through resolution by the DNS server, and you do not need to re-execute DNS resolution on the domain name, thereby improving the efficiency of domain name access again by the terminal device.
[0017] [0017] In the possible design, the DNS server can determine the condition of use information in the following ways.
[0018] [0018] First way: After obtaining the location information of the terminal device or the IP address of the terminal device from the request message, the DNS server sends the location information of the terminal device or the IP address of the terminal device to an UPF entity , so that the UPF entity determines the condition of use information based on the location information of the terminal device or the IP address of the terminal device. After determining the condition of use information, the UPF entity sends the condition of use information to the DNS server. In this way, the DNS server can obtain the usage condition information.
[0019] [0019] Second way: The DNS server sends the location information of the terminal device or the IP address of the terminal device to the UPF entity, so that the UPF entity determines at least one IP address of the terminal device and / or the range of location in which the terminal device is located, and notifies the DNS server of at least one determined IP address of the terminal device and / or the determined location range in which the terminal device is located. The DNS server can determine the defined information based on at least one IP address learned from the terminal device and / or determine the location range information based on the learned location range in which the terminal device is located, thus determining the information of location. condition of use.
[0020] [0020] Third way: After the UPF entity receives the request message sent by the terminal device, in a process of forwarding the request message to the DNS server, the UPF entity can determine the condition of use information based on the information the location of the terminal device or the IP address of the terminal device in the request message, and then send the determined usage condition information and the request message to the DNS server.
[0021] [0021] According to the design, the DNS server can obtain the condition of use information through the UPF entity.
[0022] [0022] In a possible design, the DNS server sends the indication information to the terminal device. Referral information is used to instruct the terminal device to perform DNS resolution on the domain name when the terminal device does not satisfy the condition indicated by the condition of use information.
[0023] [0023] According to the design, after the terminal device information has been changed, the terminal device will determine, based on the indication information, whether the terminal device from which the information is changed satisfies the condition indicated by the condition condition information. usage, that is, determines whether the changed IP address of the terminal device is included in at least one IP address indicated by the defined information and / or whether the changed location of the terminal device is within the location range indicated by the location range information.
[0024] [0024] In a possible design, the indication information can alternatively be conveyed in the reply message. In this way, the number of messages transmitted by the DNS server to the terminal device can be reduced, and the general signaling expenses can be reduced.
[0025] [0025] In a possible design, when the DNS server is a local DNS server, after obtaining the application server's IP address and usage condition information, the DNS server will be able to generate and store a DNS caching record . The DNS caching record includes the domain name, condition of use information, and the IP address of the application server.
[0026] [0026] When the DNS server is a root DNS server, the DNS server will need to send the reply message to the terminal device through the local DNS server. In this way, when forwarding the reply message, the local DNS server can generate and temporarily store the DNS caching record. The DNS caching record includes the same content as the previous DNS caching record.
[0027] [0027] According to the design, when the terminal device sends the request message to the local DNS server again to request domain name resolution due to several reasons (for example, if the terminal device no longer receives the message from the domain name) response, or the terminal device fails to store the DNS caching record locally, the terminal device will need to request the domain name again), the local DNS server will be able to directly determine, based on the DNS caching record temporarily stored locally , the IP address of the application server corresponding to the domain name and the condition of use information, so that the IP address of the application server and the condition of use information can be notified to the terminal device using the response, thereby improving the DNS server's domain name resolution efficiency.
[0028] [0028] According to a second aspect, an embodiment of this request additionally provides a domain name access method. The method can include the following steps.
[0029] [0029] A terminal device sends, to a DNS server, a request message including a domain name; then it receives a response message from the DNS server including an IP address of the application server and usage condition information; determines, after the terminal device information has been changed, whether the terminal device satisfies a condition indicated by the condition of use information; and will perform DNS resolution on the domain name when the terminal device does not satisfy the condition indicated by the condition of use information. The application server matches the domain name, and the usage condition information indicates a condition in which the terminal device accesses the domain name using the application server's IP address.
[0030] [0030] When the terminal device information is changed and the terminal device no longer satisfies the condition indicated by the usage condition information, the application server previously obtained through the resolution may no longer be the application server that is the most suitable to the terminal device. In this case, according to the method, the terminal device can obtain another suitable application server by re-executing the DN resolution in the domain name. Therefore, in the method, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system is also avoided.
[0031] [0031] In a possible design, the terminal device receives indication information from the DNS server, and determines, based on indication information, whether the terminal device satisfies the condition indicated by the condition of use information. Referral information is used to instruct the terminal device to perform DNS resolution on the domain name when the terminal device does not meet the condition indicated by the condition of use information.
[0032] [0032] In a possible design, the condition of use information includes at least one information among the defined information and the location range information. The defined information indicates at least one IP address of the terminal device, and the location range information indicates a location range in which the terminal device is located.
[0033] [0033] When the condition of use information includes the defined information, that the terminal device does not satisfy the condition indicated by the condition of use information includes: an IP address of the terminal device is changed and the changed IP address of the terminal device is not included in at least one IP address indicated by the defined information; and / or
[0034] [0034] when the condition of use information includes the location range information, that the terminal device does not meet the condition indicated by the condition of use information includes: a location of the terminal device is changed and the changed location of the terminal device is not is within the location range indicated by the location range information.
[0035] [0035] When the IP address of the terminal device is one of the IP addresses indicated by the defined information or the location of the terminal device is within the location range indicated by the location range information, the application server corresponding to the domain name obtained by DNS server through resolution may still be the most suitable application server. For example, the application server is even closer to the terminal device. In this way, the terminal device can continue to perform data transmission with the application server based on the application server's IP address. When the changed IP address of the terminal device is not included in the IP addresses indicated by the defined information or the location of the terminal device is not within the location range indicated by the location range information, the application server corresponding to the domain name obtained by DNS server through the resolution can no longer be closer to the terminal device. To ensure efficient communication of domain name access by the terminal device, the terminal device needs to re-perform DNS resolution on the domain name.
[0036] [0036] In a possible design, after receiving the response message from the DNS server, the terminal device temporarily stores a DNS caching record. The DNS caching record includes the domain name, condition of use information, and the IP address of the application server.
[0037] [0037] According to the design, the terminal device temporarily caches the DNS caching record locally, and when the terminal device additionally needs to access the domain name again sequentially, the terminal device can quickly obtain, based on the registration of temporarily caching DNS caching, the application server's IP address through resolution, thereby improving the efficiency of domain name resolution, reducing domain name access latency, and reducing the transmission of various related messages when the terminal device perform DNS resolution.
[0038] [0038] In a possible design, when the DNS caching record additionally includes lifetime (TTL) of the DNS caching record, the terminal device will determine that the terminal device does not meet the indicated condition within the TTL for the condition of use information.
[0039] [0039] Due to the fact that the DNS caching record is valid within the TTL, when determining that the IP address of the terminal device or the location of the terminal device is changed within the TTL, the terminal device will determine whether the device terminal from which the information is changed satisfies the condition indicated by the condition of use information. In this way, when the terminal device from which the information is changed still satisfies the condition indicated by the condition of use information, the terminal device can continue to perform data transmission with the application server based on the application server's IP address. in the DNS caching record.
[0040] [0040] In a possible design, the TTL is obtained by the terminal device from the reply message. In this way, the amount of messages transmitted by the local DNS server to the terminal device can be reduced, and overhead signaling expenses can be reduced.
[0041] [0041] According to a third aspect, an embodiment of this request provides a method of accessing a domain name. The method can include the following steps.
[0042] [0042] An SMF session management role entity obtains, in a procedure of establishing a first session through a terminal device, a first domain name of an application server on a first DN data network accessed by the terminal device ; obtains, in a procedure of establishing a second session through the terminal device, a second domain name of an application server in a second DN accessed by the terminal device; and send referral information to the terminal device when the first domain name and second domain name include the same domain name, where referral information is used to instruct the terminal device to perform DNS resolution on the domain name .
[0043] [0043] The first DN and the second DN are different area networks. Due to the mobility of the terminal device, when the terminal device moves after establishing the first session, when the second DN is closer to the terminal device than the first DN, the terminal device will access the second DN that is closest to the terminal device to save network resources. According to the method, when determining that the second domain name in the second DN currently accessed by the terminal device includes the same domain name as the first domain name in the first DN previously accessed by the terminal device, the SMF entity will instruct the terminal device to re-perform DNS resolution on the domain name. In this way, the terminal device will be able to rerun DNS resolution on the domain name to obtain a more suitable application server on the second DN, and then perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system is also avoided.
[0044] [0044] In a possible design, the SMF entity can obtain, from a PCF entity or an NEF entity, the first domain name of the application server in the first DN and the second domain name of the application server in the second DN .
[0045] [0045] In a possible design, in a scenario where the SMF entity cannot determine a target domain name that was accessed by the terminal device after the terminal device accesses the first DN, the first domain name and the second name domain names include the same domain name including any of the following three cases.
[0046] [0046] First case: The first domain name is completely the same as the second domain name (the first domain name and the second domain name have the same number of domain names and the same domain names). For example, the first domain name includes Baidu and Sina, and the second domain name includes Baidu and Sina.
[0047] [0047] Second case: Each domain name in the first domain name is included in the second domain name (the number of domain names included in the second domain name is greater than the number of domain names included in the first domain name domain). For example, the first domain name includes Baidu and
[0048] [0048] Third case: The first domain name and the second domain name include at least the same domain name. In other words, some domain names in the first domain name are included in the second domain name. For example, the first domain name includes Baidu and Sina, and the second domain name includes Sina and Tencent.
[0049] [0049] In the first case and in the second case, the second domain name will definitely include the destination domain name that was accessed by the terminal device when the terminal device accesses the first DN. However, in the third case, the second domain name can include the destination domain name. Therefore, in the first case and in the second case, the SMF entity sends the referral information to the terminal device, and the terminal device communicates with the application server on the second DN, to access the destination domain name. Therefore, in the method, the communication efficiency of the terminal device can be improved, and the transmission resources in the communications system can be saved. However, in the previous third case, the SMF entity sends the referral information to the terminal device, and the terminal device can communicate with the application server on the second DN, to access the destination domain name. In the method, the communication efficiency of the terminal device can be improved.
[0050] [0050] In a possible design, the referral information does not include any domain name in the previous design scenario. In this way, referral information can instruct the terminal device to perform DNS resolution on the domain name accessed by the terminal device after the terminal device accesses the first DN, or instruct the terminal device to perform DNS resolution on all domain names. domain currently accessed by the terminal device.
[0051] [0051] In a possible design, the referral information additionally includes the first domain name or the second domain name in the previous design scenario. In this way, the indication information can instruct the terminal device to perform DNS resolution on the first domain name (or the second domain name) currently accessed by the terminal device.
[0052] [0052] In a possible design, in a scenario in which the SMF entity can determine the target domain name that was accessed by the terminal device after the terminal device accesses the first ND, the first domain name and the second name of domains include the same domain name, that is, both the first domain name and the second domain name include the target domain name.
[0053] [0053] Due to the fact that the second domain name includes the destination domain name, the SMF entity sends the referral information to the terminal device, and the terminal device communicates with the application server on the second DN to access the name target domain name. Therefore, in the method, the communication efficiency of the terminal device can be improved, and the transmission resources in the communications system can be saved.
[0054] [0054] In a possible design, the referral information includes the destination domain name in the previous design scenario. In this way, the referral information can instruct the terminal device to perform DNS resolution on the destination domain name, thus improving the relevance of the referral information and additionally solving the problem of wasted resources.
[0055] [0055] According to a fourth aspect, an embodiment of this request additionally provides a domain name access method. The method can include the following steps.
[0056] [0056] An NEF network exposure function entity determines that the IP address information of an application server corresponding to a domain name is changed, and then notifies a PCF policy control function entity that the information from the application server is changed. IP address of the application server corresponding to the terminal device is changed.
[0057] [0057] The change in the IP address information of the application server corresponding to the domain name in the NEF entity indicates the addition of an application server corresponding to the domain name to a communications system. When the IP address is changed due to movement of the terminal device that currently accesses the domain name, the application server closest to the terminal device can also be changed (which can be changed to an application server to which the updated DNAI belongs) corresponding to the domain name). Therefore, the NEF needs to trigger a notification procedure for the SMF entity to notify, when the IP address allocated by the SMF entity to the terminal device is changed, the terminal device to re-execute DNS resolution on the domain name. According to the method, the terminal device can obtain a more suitable application server by re-executing the resolution, and additionally perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system is also avoided.
[0058] [0058] In a possible design, the application server's IP address information is a data network access identifier
[0059] [0059] In a possible design, the NEF entity sends an IP address information change notification message to the PCF entity, to notify the PCF entity that the application server's IP address information corresponding to the domain name is changed.
[0060] [0060] According to a fifth aspect, an embodiment of this request additionally provides a domain name access method. The method can include the following steps.
[0061] [0061] A PCF policy control function entity learns, from a NEF network exposure function entity, that the Internet Protocol IP address information of an application server corresponding to a domain name is changed, and then sends the referral information to an SMF session management role entity. Referral information is used to instruct the SMF entity to notify, when an IP address allocated by the SMF entity to the terminal device that currently accesses the domain name is changed, the terminal device to perform DNS resolution on the domain name.
[0062] [0062] The change in the IP address information of the application server corresponding to the domain name in the NEF entity indicates the addition of an application server corresponding to the domain name to a communications system. When the IP address is changed due to movement of the terminal device that currently accesses the domain name, the application server closest to the terminal device can also be changed (which can be changed to an application server to which the updated DNAI belongs) corresponding to the domain name). Therefore, the PCF entity instructs the SMF entity to notify, when the IP address allocated by the SMF entity to the terminal device is changed, the terminal device to re-perform DNS resolution on the domain name, and the terminal device may obtain a server from most suitable application with the resolution re-execution, and additionally perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of resources in a communications system is also avoided.
[0063] [0063] According to a sixth aspect, an embodiment of this request additionally provides a domain name access method. The method can include the following steps.
[0064] [0064] An SMF session management role entity receives referral information from a PCF policy control role entity; and
[0065] [0065] notifies, based on the indication information when the IP address allocated by the SMF entity for a terminal device is changed, the terminal device to perform DNS resolution on a domain name, where the terminal device is a terminal device that currently access the domain name.
[0066] [0066] The change in the IP address information of the application server corresponding to the domain name in the NEF entity indicates the addition of an application server corresponding to the domain name to a communications system. When the IP address is changed due to movement of the terminal device that currently accesses the domain name, the application server closest to the terminal device can also be changed (which can also be changed to an application server to which DNAI belongs) updated corresponding to the domain name). Therefore, the SMF entity will notify, when the IP address allocated by the SMF entity to the terminal device is changed, the terminal device to re-execute DNS resolution on the domain name, and the terminal device may obtain a more suitable application server with the rerun the resolution, and additionally perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system can also be avoided.
[0067] [0067] According to a seventh aspect, an embodiment of this request provides a DNS server, including a unit or a means to perform the previous steps of the first aspect.
[0068] [0068] According to an eighth aspect, an embodiment of this application provides a terminal device, including a unit or a means for performing the previous steps of the second aspect.
[0069] [0069] According to a ninth aspect, an embodiment of this request provides an SMF entity, including a unit or a means to perform the previous steps of the third or sixth aspect.
[0070] [0070] According to a tenth aspect, an embodiment of this request provides an NEF entity, including a unit or a means to perform the previous steps of the fourth aspect.
[0071] [0071] According to an eleventh aspect, an embodiment of this request provides a PCF entity, including a unit or a means to perform the previous steps of the fifth aspect.
[0072] [0072] According to a twelfth aspect, an embodiment of this request provides a DNS server, including at least one processing element and at least one storage element. At least one storage element is configured to store a program and data, and at least one processing element is configured to execute the method according to the first aspect of this application.
[0073] [0073] According to a thirteenth aspect, an embodiment of this application provides a terminal device, including at least one processing element and at least one storage element. At least one storage element is configured to store a program and data, and at least one processing element is configured to execute the method according to the second aspect of this application.
[0074] [0074] According to a fourteenth aspect, an embodiment of this request provides an SMF entity, including at least one processing element and at least one storage element. At least one storage element is configured to store a program and data, and at least one processing element is configured to execute the method according to the third or sixth aspect of this application.
[0075] [0075] According to a fifteenth aspect, an embodiment of this request provides an NEF entity, including at least one processing element and at least one storage element. At least one storage element is configured to store a program and data, and at least one processing element is configured to execute the method according to the fourth aspect of this application.
[0076] [0076] According to a sixteenth, an embodiment of this request provides a PCF entity, including at least one processing element and at least one storage element. At least one storage element is configured to store a program and data, and at least one processing element is configured to execute the method in accordance with the fifth aspect of this application.
[0077] [0077] According to a seventeenth aspect, an embodiment of this application additionally provides a computer storage medium. The storage medium stores a software program. When read and executed by one or more processors, the software program can implement the method according to the first aspect to the sixth aspect or any design of any of the previous aspects.
[0078] [0078] According to an eighteenth, an embodiment of this request additionally provides a computer program product including an instruction. When run on a computer, the computer program product allows the computer to perform the methods according to the previous aspects.
[0079] [0079] According to a nineteenth aspect, an embodiment of this application provides a chip system. The chip system includes a processor, configured to support any one of these: a terminal device, a DNS server, an SMF entity, an NEF entity, or a PCF entity, in the implementation of a function according to the previous corresponding aspects. In a possible design, the chip system additionally includes a memory. The memory is configured to store a program instruction and data that are needed by the device. The chip system can include a chip, or it can include a chip and another discrete device.
[0080] [0080] In a solution provided in the embodiments of this request, a DNS server performs resolution on a domain name requested by a terminal device, and then sends, to the terminal device, the condition of use information and an IP address of a server corresponding to the domain name obtained through the resolution. The condition of use information indicates a condition that must be met when the terminal device can access the domain name using the IP address for the application server. In this way, the terminal device can perform, based on the IP address received from the application server, data transmission with the application server, and when the information from the terminal device is changed due to the movement of the terminal device, and the terminal device no longer satisfies the condition by the condition of use information, the terminal device may re-execute DNS resolution on the domain name. When the terminal device information is changed and the terminal device no longer satisfies the condition indicated by the usage condition information, the application server previously obtained through the resolution may no longer be the application server that is the most suitable for the device terminal. In this case, according to the solution, the terminal device can obtain another suitable application server by re-executing the DNS resolution on the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, avoiding the waste of transmission resources in a communications system. BRIEF DESCRIPTION OF THE DRAWINGS
[0081] [0081] Figure 1 is an architectural diagram of a communications system according to an embodiment of this request.
[0082] [0082] Figures 2A and Figure 2B are flowcharts of establishing a session in accordance with an embodiment of this request.
[0083] [0083] Figure 3 is a flow chart of a domain name access method according to an embodiment of this request.
[0084] [0084] Figures 4A and Figure 4B are flowcharts of an example of the domain name access method according to an embodiment of this application.
[0085] [0085] Figure 5 is a flowchart of another domain name access method according to an embodiment of this request.
[0086] [0086] Figures 6A and 6B are flowcharts of an example of the other domain name access method according to an embodiment of this application.
[0087] [0087] Figure 7 is a flowchart of yet another domain name access method in accordance with an embodiment of this request.
[0088] [0088] Figures 8A, 8B and 8C are flowcharts of an example of yet another domain name access method in accordance with an embodiment of this application.
[0089] [0089] Figure 9 is a structural diagram of a first DNS server according to an embodiment of this request.
[0090] [0090] Figure 10 is a structural diagram of a first terminal device according to an embodiment of this application.
[0091] [0091] Figure 11 is a structural diagram of a first SMF entity according to an embodiment of this request.
[0092] [0092] Figure 12 is a structural diagram of a first NEF entity according to an embodiment of this application.
[0093] [0093] Figure 13 is a structural diagram of a first PCF entity according to an embodiment of this application.
[0094] [0094] Figure 14 is a structural diagram of a second SMF entity according to an embodiment of this request.
[0095] [0095] Figure 15 is a structural diagram of a second DNS server according to an embodiment of this request.
[0096] [0096] Figure 16 is a structural diagram of a second terminal device according to an embodiment of this application.
[0097] [0097] Figure 17 is a structural diagram of a third SMF entity according to an embodiment of this request.
[0098] [0098] Figure 18 is a structural diagram of a second NEF entity according to an embodiment of this application.
[0099] [0099] Figure 19 is a structural diagram of a second PCF entity according to an embodiment of this application.
[00100] [00100] Figure 20 is a structural diagram of a fourth SMF entity according to an embodiment of this request. DESCRIPTION OF THE ACCOMPLISHMENTS
[00101] [00101] This application provides a domain name access method and device to improve the communication efficiency of a terminal device. The method and the device are designed based on the same concept as the invention. Because the troubleshooting principles for the method and the device are similar, implementations of the device and the method can be referenced mutually. The details of repeated parts will not be described again.
[00102] [00102] In a solution provided in the embodiments of this request, a DNS server performs the resolution on a domain name requested by a terminal device, and then sends, to the terminal device, the condition of use information and an IP address of a application server corresponding to the domain name obtained through the resolution. The condition of use information indicates a condition that must be met when the terminal device can access the domain name using the application server's IP address. In this way, the terminal device can perform, based on an IP address received from the application server, data transmission with the application server, and when the terminal device information is changed due to the movement of the terminal device, and the device terminal no longer meets the condition indicated by the condition of use information, the terminal device may re-execute DNS resolution on the domain name. When the terminal device information is changed and the terminal device no longer satisfies the condition indicated by the usage condition information, the application server previously obtained through the resolution can no longer be the application server that is the most suitable for the device terminal. In this case, according to the solution, the terminal device can obtain another suitable application server by re-executing the DNS resolution on the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system is also avoided.
[00103] [00103] Below, some terms are described in this application to help those skilled in the art to have a better understanding.
[00104] [00104] (1) A terminal device is also referred to as a user equipment (EU), a mobile station (mobile station (MS)), a mobile terminal (mobile terminal (MT)), or the like, and it is a device that provides voice and / or data connectivity for a user. For example, the terminal device includes a portable device or a device installed in the vehicle featuring a wireless function. Currently, the terminal device can be a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a mobile internet device (MID), a wearable device, a virtual reality device (virtual reality (VR)), an augmented reality (AR) device, a wireless terminal in industrial control (industrial control), a wireless terminal in self-conducting (self driving), a wireless terminal in surgery remote medical surgery, a wireless terminal on a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a terminal without wire in a smart home, or similar.
[00105] [00105] (2) A DNS server is a domain name resolution device in a DNS. The DNS server can perform, using a domain name resolution mechanism, the resolution on a domain name requested by the terminal device to obtain an IP address from an application server corresponding to the domain name.
[00106] [00106] Optionally, there can be a plurality of DNS servers distributed in the DNS in a hierarchical architecture, for example, a local DNS server and a root DNS server.
[00107] [00107] In the domain name resolution mechanism, DNS performs the resolution on the domain name successively through the servers presenting an ascending order until the IP address of the application server corresponding to the domain name is obtained. The details of the domain name resolution mechanism will not be described in the embodiments of this application again.
[00108] [00108] (3) DNS resolution means that the DNS server performs domain name resolution using the domain name resolution mechanism. The DNS resolution is proposed to distinguish itself from the execution, through the terminal device and the DNS server, of the resolution in the domain name using a DNS caching record.
[00109] [00109] (4) Condition information of use of the IP address of the application server indicates a condition in which the terminal device must satisfy when the terminal device can access the domain name using the IP address of the application server. Therefore, when the terminal device satisfies the condition indicated by the condition of use information, the terminal device can access the domain name using the IP address of the application server; or when the terminal device does not satisfy the condition indicated by the condition of use information, the terminal device will no longer be able to access the domain name using the application server's IP address, and will need to re-run DNS resolution on the domain name.
[00110] [00110] Optionally, the condition can include an IP address condition and / or a location condition, but is not limited to these.
[00111] [00111] (5) Defined information indicates at least one IP address of the terminal device. When the usage condition information from the application server's IP address includes the defined information, the condition indicated by the usage condition information will be that: an IP address of the terminal device is included in at least one IP address indicated by the information defined.
[00112] [00112] The IP address can be an Internet Protocol version 4 address (internet protocol version 4 (PPv4) or a prefix (prefix) of Internet Protocol version 6 (internet protocol version 6 (IPv6)).
[00113] [00113] Optionally, the defined information can be an IP address segment, for example, 10.10.1.85 to 10.10.1.125; or it can be a set of IP addresses, for example, 10.10.1.85,
[00114] [00114] (6) Location range information indicates a location range of the terminal device. When the condition of use information from the IP address of the application server includes the location range information, the condition indicated by the condition of use information will be that: a location of the terminal device is within the location range indicated by the information location range.
[00115] [00115] Optionally, the location range can be a latitude and longitude range, a range in which a specified administrative unit is located, a range of specified area, or the like.
[00116] [00116] (7) A request message is also referred to as a domain name resolution request message and will be sent to the DNS server when the terminal device requests the DNS server to perform resolution on the domain name. The request message includes the domain name requested by the terminal device.
[00117] [00117] (8) A reply message, also referred to as a domain name resolution reply message, matches the request message and is sent to the terminal device after the DNS server obtains the IP address from the application server corresponding to the domain name through the resolution. The response message includes the IP address of the application server.
[00118] [00118] In the embodiments of this request, the reply message includes the IP address of the application server, and additionally includes the condition information for use of the IP address of the application server. Thus, when the terminal device does not satisfy the condition indicated by the condition of use information, the terminal device will no longer be able to access the domain name using the application server's IP address, and will need to re-run DNS resolution on behalf of domain.
[00119] [00119] (9) The DNS caching record is stored in a cache of the DNS server or the terminal device and is used to record a result of the resolution performed by the DNS server in the domain name.
[00120] [00120] Optionally, the DNS caching record can include the domain name and the IP address of the application server corresponding to the domain name.
[00121] [00121] Optionally, during a domain name resolution process, if the DNS server additionally obtains the application server's IP address usage condition information obtained through the resolution, the DNS caching record will include the name of domain, condition of use information, and the IP address of the application server corresponding to the domain name.
[00122] [00122] In addition, optionally, the DNS caching record additionally includes TTL from the DNS caching record. That is, the TTL will start when the DNS caching record is successfully cached, and the DNS caching record is valid within the TTL and becomes invalid after the TTL.
[00123] [00123] (10) The term "and / or" describes an association relationship between associated objects and represents that three relationships can exist. For example, A and / or B can represent the following three cases: Only A exists, both A and B exist, and only B exists. The "/" character usually indicates an "or" relationship between the associated objects.
[00124] [00124] It will be noted that, in this application, the term "plurality of" indicates two or more than two.
[00125] [00125] Furthermore, it will be understood that, in the descriptions of this application, the terms such as "first" and "second" are merely used for the purpose of distinguishing descriptions and are not intended to indicate or suggest relative importance or to indicate or suggest a sequence.
[00126] [00126] The embodiments of this application are described in detail below with reference to the attached drawings.
[00127] [00127] Figure 1 shows a possible architecture of a communications system to which a domain name access method provided in the embodiments of this request is applied. With reference to Figure 1, the communications system includes: a terminal device 101, an access network (AN) device 102, a plurality of network element devices in a central network, a DNS server 109 in a DNS, and a data network (DN).
[00128] [00128] As shown in the figure, the network element devices in the central network include: control plane function (CPF) entities such as an access and mobility management entity (access and mobility) management function (AMF)) 103, a session management function entity (SMF) 104, a policy control function entity (PCF) 105, and a policy function entity network exposure function (NEF) 106, a user plane function (UPF) 107 entity, and a unified data management entity (UDM) 110.
[00129] [00129] The DN can be the Internet (Internet), an IP multimedia service network (IP Multi-media Service (IMS)), an area network (ie, a local area network, for example, a computing network mobile edge computing (MEC), or similar.
[00130] [00130] The DN includes an application server 108. The application server 108 provides a commercial service for the terminal device 101 with the execution of data transmission with the terminal device 101.
[00131] [00131] The AN 102 device is a device that connects terminal device 101 to a wireless network in the communications system. The AN device is a node on a radio access network, and can also be referred to as a base station, or it can be referred to as a radio access network (RAN) node (or device). , some examples of the AN device are a gNB, a transmission reception point (transmission reception point (RP)), an evolved Node B (evolved Node B (eNB)), a radio network controller (RNC )), a B node (Node B (NB)), a base station controller (BSC), a base transceiver station (base transceiver station (BTS)), a home base station (e.g. a domestic evolved NodeB or a domestic Node B (Node B (HNB)), a base band unit (base band unit (BBU)), an access point (AP) for wireless fidelity ( WiFi)), and the like.
[00132] [00132] The central network is configured to connect the terminal device 101 to the application server 108 in a DN that can implement a service of the terminal device 101. The functions of the network element devices in the central network are described below.
[00133] [00133] The AMF 103 entity can be configured to be responsible for procedures such as registration, mobility management, and updating of the tracking area of the terminal device 101.
[00134] [00134] The SMF 104 entity can be configured to be responsible for the session management (including session establishment, session modification and session release) of the terminal device 101, selection and reselection of the UPF entity 107, IP address allocation and control QoS of terminal device 101, and the like.
[00135] [00135] The PCF 105 entity can be configured to be responsible for the functions, such as a policy control decision function.
[00136] [00136] The NEF entity 106 may be responsible for transferring information between the application server 108 and a network function entity (for example, the SMF entity 104, the application server 108, or the PCF 105 entity), and storing information obtained from application server 108 or the network role entity, for example, storing a match between a domain name and IP address information from the application server.
[00137] [00137] The UDM 110 entity can be configured to manage subscription data from the terminal device 101 and registration information related to the terminal device 101.
[00138] [00138] The entity of UPF 107 can be configured to forward the data of the user plan of the terminal device 101.
[00139] [00139] The previous entities in the central network can be network elements implemented on dedicated hardware, or they can be examples of software running on dedicated hardware, or examples of a virtualization function on an appropriate platform. For example, the previous virtualization platform may be a cloud platform.
[00140] [00140] Furthermore, in the communications system, the terminal device 101, the AN device, the network element devices in the central network, the application server 108 in the DN, and the DNS server 109 are connected using interfaces corresponding, as shown in Figure 1. The details will not be described here again.
[00141] [00141] It will be noted that the communications system shown in Figure 1 does not constitute a limitation to a communications system to which the embodiments of this application can be applied. Therefore, the method provided in the embodiments of this application can also be applied to a 2a mobile communications system. 2nd generation (2G), for example, a Global System of Mobile Communication (GSM) and a General Packet Radio Service (GPRS) system; or it can be a 3rd generation (3G generation) mobile communications system, for example, a Universal Mobile Telecommunications System (UMTS); or it can be applied to a 4th generation (4G) mobile communications system; and can be applied to multiple mobile communications networks of 5a. generation (5th generation (5G)) or several future communications networks.
[00142] [00142] In the communications system shown in Figure 1, the terminal device can perform session establishment (hereinafter, it is described using a packet data unit (PDU) session establishment as a example) using a procedure shown in Figures 2A and 2B, to perform data transmission with the application server in the DN, thus implementing a terminal device service. With reference to Figures 2A and 2B, a procedure for establishing The terminal device session includes the following steps.
[00143] [00143] S201. The terminal device sends a session establishment request message (PDU) to an AMF entity, where the session establishment request message includes a PDU session identifier (ID).
[00144] [00144] Optionally, the message of request of establishment of session can be included in a message of layer without access (Non Access Stratum (NAS)). The session establishment request message can additionally include at least one of the following: single-network slice selection assistance information (S-NSSAI) assistance information, an identifier (DN number (DNN) ) of a DN that the terminal device requests to access, and N1 session management information (session management (SM)). S-NSSAI is used for network slice selection.
[00145] [00145] S202: The AMF entity selects a suitable SMF entity for the terminal device.
[00146] [00146] S203: The AMF entity sends a session management request message (SM Request) to the selected SMF entity, where the session management request message includes the session establishment request message.
[00147] [00147] Optionally, the session management request message additionally includes at least one of the following: an identifier (for example, a subscriber permanent identifier (SUPI) or a temporary subscriber identifier) of the terminal device, the S- NSSAI, the PDU session ID, the DNN, an AMF entity ID, the NI SM information, the location information (user location information) of the terminal device, and a type of access technology (access technology type).
[00148] [00148] S204: The SMF entity obtains subscription data (subscription data) from the terminal device of an UDM entity during a procedure for obtaining subscription data.
[00149] [00149] The subscription data includes at least one of the following: (one) type (s) of authorized PDU, (one) mode (s) of authorized session and service continuity, and file / description of quality of service (quality of service (QoS).
[00150] [00150] The procedure for obtaining signature data includes the following steps:
[00151] [00151] The procedure for obtaining signature data includes:
[00152] [00152] a. send, through the SMF entity, a subscription data request message to the UDM entity; and
[00153] [00153] b. return, through the UDM entity to the SMF entity, a subscription data response message that conducts the subscription data.
[00154] [00154] S205: The communications system performs a PDU session authentication procedure.
[00155] [00155] S206. The SMF selects a PCF entity for the terminal device, and obtains a policy and charging control (PCC) rule from the PCF entity.
[00156] [00156] S207: The SMF entity selects, based on information such as the location information and the signature data of the terminal device and SSC mode (s), a UPF entity suitable for the terminal device, and allocates, based on the PDU session, an IP address for the terminal device.
[00157] [00157] Optionally, the IP address can be an IPv4 address or an IPv6 prefix.
[00158] [00158] S208: When the PCC rule obtained by the SMF entity in S206 is a dynamic PCC rule, the SMF entity will obtain an updated PCC rule from the PCF entity.
[00159] [00159] It will be noted that if the PCC rule obtained by the SMF entity in S206 is not the dynamic PCC rule, the SMF entity will not be able to execute S208. Therefore, S208 is an additional step.
[00160] [00160] S209: If the communications system does not execute S205, the SMF entity will start an N4 session establishment procedure (N4 Session Establishment procedure) for the selected UPF entity; or if the communications system runs S205, the SMF entity will initiate an N4 session modification procedure (N4 Session Modification procedure) for the UPF.
[00161] [00161] With the start of the N4 session establishment / modification procedure, the SMF entity can provide rules for detection, execution and reporting of packets (packet detection, enforcement and reporting rules) for the UPF entity. If the SMF entity allocates core network (CN) information (CN tunnel information), the SMF entity will also send the CN tunnel information to the UPF entity.
[00162] [00162] S210: The SMF entity sends a session management request confirmation (SM Request ACK) to the AMF entity.
[00163] [00163] Session management request confirmation can additionally include:
[00164] [00164] N2 session management information (SM information), for example, PDU session ID, QoS configuration (profile), or CN tunnel information; and
[00165] [00165] the session management information N1, for example, a PDU session establishment accept message (including a QoS rule or SSC mode (s)).
[00166] [00166] S211: The AMF entity sends an N2 session request message (N2 PDU session Request) to an AN device, where the N2 session request message includes the N2 section management information and the establishment acceptance message PDU session.
[00167] [00167] S212. The AN device performs signaling interworking with the terminal device to configure a radio resource. Upon execution of the procedure, the AN device sends the PDU session establishment acceptance message obtained from the SMF entity to the terminal device.
[00168] [00168] S213: The AN device sends an N2 session request confirmation (N2 PDU session request ACK) to the AMF entity, where the N2 session request confirmation includes an N2 message (N2 information), and the N2 message can include AN tunnel information (AN tunnel information).
[00169] [00169] After S213, the terminal device can send the uplink data to the UPF entity, as shown in the figure.
[00170] [00170] S214: The AMF entity sends a session management update message (SM update) to the SMF entity.
[00171] [00171] The session management update message additionally includes the N2 session management information (N2 SM information).
[00172] [00172] S215: The SMF entity initiates the N4 session modification procedure (N4 session modification procedure) to the UPF, and sends the AN tunnel information and the CN tunnel information to the UPF entity in the procedure.
[00173] [00173] S216. The SMF entity sends a session management update confirmation (SM update ACK) to the AMF entity.
[00174] [00174] Optionally, in the previous procedure, when the IP address allocated by the SMF entity to the terminal device is the IPv4 address, the SMF entity can send the IP address of the terminal device to the terminal device via S210, S211 and S212, this that is, the IP address for the terminal device is conducted in the message transmitted in the previous steps, as shown in the figure.
[00175] [00175] S217: When a PDU type is IPv6, the IP address allocated by the SMF entity to the terminal device will be the IPv6 prefix, and the SMF entity will send an advertisement message from the router (router advertisement) to the terminal device through the entity UPF, where the IPv6 router announcement message includes the IPv6 prefix of the terminal device.
[00176] [00176] In this case, the message transmitted in the previous S210, S211 and S212 does not lead to an IP address of the terminal device.
[00177] [00177] After S216 or S217, the terminal device can receive downlink data sent by the UPF entity, as shown in the figure.
[00178] [00178] Through the previous procedure, the terminal device can establish the PDU session, thus implementing a terminal device service.
[00179] [00179] After establishing the PDU session, when the terminal device needs to access a destination domain name, the terminal device can send a domain name resolution request message to the DNS server through the UPF entity. After the DNS server obtains an IP address from an application server corresponding to the destination domain name through resolution, a domain name resolution response message including the IP address of the application server can alternatively be returned to the device terminal through the UPF entity. In this way, the terminal device can perform, based on the IP address of the application server, data transmission with the application server, thus accessing the destination domain name.
[00180] [00180] One embodiment of this request provides a domain name access method, applied to the communications system shown in Figure 1. With reference to Figure 3, a method procedure includes the following steps.
[00181] [00181] S301: A terminal device sends a request message to a DNS server, where the request message includes a domain name requested by the terminal device.
[00182] [00182] Optionally, the request message additionally includes location information of the terminal device or an IP address of the terminal device. The location information of the terminal device can be the location information of an AN device currently accessed by the terminal device.
[00183] [00183] In this embodiment of this request, before accessing the domain name, the terminal device must successfully establish a session. In this way, in a domain name procedure, the terminal device can perform the communication interaction with the DNS server through an UPF entity that serves the terminal device in the communications system, that is, the terminal device can send the message of request to the DNS server through the UPF entity. Correspondingly, the DNS server can alternatively send a reply message to the terminal device subsequently via the UPF entity.
[00184] [00184] S302. After receiving the request message from the terminal device, the DNS server performs resolution on the domain name, to obtain an IP address from an application server corresponding to the domain name.
[00185] [00185] The DNS server can perform domain name resolution using a DNS domain name resolution mechanism. For example, the DNS server selects an application server closest to the terminal device. The details of the specific process are not described in the embodiments of this order again.
[00186] [00186] S303. The DNS server sends the response message to the terminal device, where the response message includes the application server's IP address and usage condition information, the usage condition information indicating a condition where the terminal device accesses the name domain name using the application server's IP address.
[00187] [00187] Optionally, the condition of use information can include at least one information among the defined information and the location range information.
[00188] [00188] The defined information indicates at least one IP address of the terminal device. Location range information indicates a location range in which the terminal device is located.
[00189] [00189] Before executing S303, the DNS server additionally needs to determine the condition of use information. Optionally, the DNS server can obtain the condition of use information based on the request message.
[00190] [00190] Optionally, when the request message additionally includes the location information of the terminal device or the IP address of the terminal device, the DNS server will obtain the condition of use information based on the location information of the terminal device or the IP address of the terminal device included in the request message.
[00191] [00191] At least one IP address indicated by the defined information included in the condition of use information includes the IP address of the terminal device; or
[00192] [00192] the location range indicated by the location range information included in the condition of use information includes a location indicated by the location information of the terminal device.
[00193] [00193] In the communications system, the UPF entity stores a pool of addresses, and allocates, based on the location information of the terminal devices, IP addresses in the address pool for the corresponding terminal devices. Therefore, in this implementation of this request, the DNS server can obtain the condition of use information through the UPF entity. The following cases are specifically included.
[00194] [00194] First case: After obtaining the location information of the terminal device or the IP address of the terminal device of the request message, the DNS server sends the location information of the terminal device or the IP address of the terminal device to the UPF entity , so that the UPF entity determines the condition of use information based on the location information of the terminal device or the IP address of the terminal device. After determining the condition of use information, the UPF entity sends the condition of use information to the DNS server. In this way, the DNS server can obtain the usage condition information.
[00195] [00195] Optionally, in the first possible implementation of the first case, the UPF entity can determine the defined information based on the location information of the terminal device by performing the following steps.
[00196] [00196] The UPF entity tracks, based on the stored location information of a plurality of terminal devices, the location information of a plurality of destination terminal devices (which may include the terminal device) within the same range. area that the location information of the terminal device. The area strip can be a predefined area strip (for example, an administrative unit, such as a district, county, or city), or an area strip in which the distance is defined using location information of the terminal device as a center. This is not limited to this order.
[00197] [00197] The UPF entity determines, based on the location information tracked from the plurality of destination terminal devices, the IP addresses allocated to the plurality of destination terminal devices, and determines the information defined based on the plurality IP addresses of target terminal devices. Optionally, the IP addresses indicated by the defined information can be the IP addresses of the plurality of destination terminal devices, or include at least the IP addresses of the plurality of destination terminal devices.
[00198] [00198] For example, the IP addresses of the three destination terminal devices are 10.10.1.85, 10.10.1.87 and 10.10.1.93, and the IP addresses indicated by the defined information can be
[00199] [00199] Optionally, in the second possible implementation of the first case, the UPF entity may alternatively determine the information defined based on the IP address of the terminal device by performing the following steps.
[00200] [00200] The UPF entity may divide, based on the area range in which the stored location information of each terminal device is located, the stored location information of the plurality of terminal devices to generate a plurality of sets of location information ; and the UPF entity then groups the IP addresses of the terminal devices corresponding to the location information of the terminal devices included in each location information defined in a set of corresponding IP addresses.
[00201] [00201] The UPF entity determines the set of IP addresses to which the IP address of the terminal device belongs, and generates the information defined based on the set of IP addresses. The IP addresses indicated by the defined information can be the IP addresses in the set of IP addresses, or include at least the IP addresses in the set of IP addresses.
[00202] [00202] Optionally, in the third possible implementation of the first case, the UPF entity can alternatively determine the location range information based on the location information of the terminal device by performing the following steps.
[00203] [00203] The UPF entity determines, from a plurality of predefined location bands (for example, an area band in which an administrative unit, such as a district, county, or city is located), a band of destination location to which a location indicated by the location information of the terminal device belongs, and then determines the location range information based on the destination location range; or the UPF entity determines a location indicated by the location information of the terminal device, and then determines that an area range over which the distance is defined using a location of the terminal device as a center is a destination location range, and then determines the location range information based on the destination location range.
[00204] [00204] Optionally in the fourth possible implementation of the first case, the UPF entity can alternatively determine the location range information based on the IP address of the terminal device by performing the following steps
[00205] [00205] The UPF entity may divide, based on the area range in which the stored location information of each terminal device is located, the stored location information of the plurality of terminal devices to generate a plurality of sets of location information ; and the UPF entity then groups the IP addresses of the terminal devices corresponding to the location information of the terminal devices included in each location information defined in a set of corresponding IP addresses.
[00206] [00206] The UPF entity determines the set of IP addresses to which the IP address of the terminal device belongs, and determines that an area range to which the set of location information corresponding to the set of IP addresses belongs is a location range of destination, and you can finally determine the location range information based on the destination location range.
[00207] [00207] Second case: The DNS server sends the location information of the terminal device or the IP address of the terminal device to the UPF entity, so that the UPF entity determines at least one IP address of the terminal device and / or the range of location in which the terminal device is located, and notifies the DNS server of at least one determined IP address of the terminal device and / or the determined location range in which the terminal device is located. In this way, the DNS server can determine the defined information based on at least one IP address learned from the terminal device and / or determine the location range information based on the learned location range in which the terminal device is located, thereby determining the condition of use information.
[00208] [00208] Optionally, in the first possible implementation of the second case, for a specific process in which the UPF entity determines at least one IP address of the terminal device based on the location information of the terminal device, refer to the description of determining the addresses IP of the plurality of the target terminal devices in the first possible implementation of the first case. The details will not be described here again.
[00209] [00209] Optionally, in the second possible implementation of the second case, for a specific process in which the UPF entity determines, based on the IP address of the terminal device, at least one IP address of the terminal device, refer to the description of determining the set of IP addresses to which the IP address of the terminal device belongs in the second possible implementation of the first case. The details will not be described here again.
[00210] [00210] Optionally, in the third possible implementation of the second case, for a specific process in which the UPF entity determines, based on the location information of the terminal device, the location range in which the terminal device is located, refer to the description of determining the target location range in the third possible implementation of the first case. The details will not be described here again.
[00211] [00211] Optionally, in the fourth possible implementation of the second case, for a specific process in which the UPF entity determines, based on the IP address of the terminal device, the location range in which the terminal device is located, refer to the description to determine the target location range in the fourth possible implementation of the first case. The details will not be described here again.
[00212] [00212] Third case: After the UPF entity receives the request message sent by the terminal device at S301, in a process of forwarding the request message to the DNS server, the UPF entity can determine the usage condition information based on the location information of the terminal device or the IP address of the terminal device in the request message, and then send the determined condition of use information and the request message to the DNS server. Optionally, the UPF entity can alternatively send the determined condition of use information to the DNS server using the request message. In other words, the request message sent to the DNS server can include the determined usage condition information. After obtaining the condition of use information and obtaining the IP address of the application server through the resolution, the DNS server sends the reply message to the terminal device.
[00213] [00213] Optionally, in the previous third case, for a specific process in which the UPF entity determines the condition of use information based on the location information of the terminal device or the IP address of the terminal device, refer to the descriptions in the first possible implementation until the fourth possible implementation of the first case. The details will not be described here again.
[00214] [00214] In a possible design, the DNS server sends the condition of use information to the terminal device with the execution of S303, and then the terminal device determines, when the IP address of the terminal device or the location of the terminal device are changed , if the changed terminal device satisfies the condition indicated by the condition of use information.
[00215] [00215] In another possible design, the DNS server notifies the terminal device of a way of processing the condition of use information, that is, the DNS server sends the indication information to the terminal device, where the indication information is used to instruct the terminal device to perform DNS resolution on the domain name when the terminal device does not satisfy the condition indicated by the condition of use information. In this way, before the information of the terminal device (the IP address of the terminal device and / or the location of the terminal device) is changed, the terminal device receives the indication information from the DNS server. After the terminal device information is changed, the terminal device determines, based on the indication information, whether the terminal device from which the information is changed satisfies the condition indicated by the condition of use information, that is, it determines whether the address Changed IP of the terminal device is included in at least one IP address indicated by the defined information and / or if the changed location of the terminal device is within the location range indicated by the location range information.
[00216] [00216] Optionally, the indication information can also be carried in the reply message. In this way, the amount of messages transmitted by the DNS server to the terminal device can be reduced, and overhead signaling expenses can also be reduced.
[00217] [00217] In addition, when the DNS server is a local DNS server, after obtaining the application server's IP address and usage condition information, the DNS server may additionally generate a DNS caching record, and temporarily store the DNS caching record. The DNS caching record includes the domain name, condition of use information, and the IP address of the application server.
[00218] [00218] When the DNS server is a root DNS server, the DNS server will need to send the reply message to the terminal device through the local DNS server. When forwarding the response message, the local DNS server can generate and temporarily store the DNS caching record.
[00219] [00219] Thus, when the terminal device sends the request message to the local DNS server again to request the domain name resolution due to several reasons (for example, if the terminal device no longer receives the reply message, or the terminal device fails to store the DNS caching record locally, the terminal device will need to request the domain name again), the local DNS server will be able to directly determine, based on the DNS caching record temporarily stored locally, the address Application server IP corresponding to the domain name and usage condition information, so that the application server IP address and usage condition information can be notified to the terminal device using the reply message, improving thus the efficiency of resolving the domain name of the DNS server.
[00220] [00220] Optionally, the DNS caching record generated by the local DNS server additionally includes TTL from the DNS caching record.
[00221] [00221] Optionally, the local DNS server can add the TTL to the reply message, or send the TTL to the terminal device using another independent message, so that the DNS caching record generated by the terminal device additionally includes the TTL. In this way, the local DNS server DNS and the terminal device can maintain the DNS caching records of the local DNS server and the terminal device synchronously.
[00222] [00222] S304. After receiving the reply message from the DNS server, the terminal device will perform DNS resolution on the domain name when the terminal device does not satisfy the condition indicated by the condition of use information.
[00223] [00223] After receiving the response message from the DNS server, the terminal device can perform data transmission with the application server using the IP address of the application server in the response message.
[00224] [00224] Due to the mobility of the terminal device, when the terminal device is in a mobile state, the AN device accessed by the terminal device and the UPF entity serving the terminal device can be changed, and the SMF entity in the communications system can also be changed. again select another UPF entity for the terminal device based on the real-time location information of the terminal device or a charge status of the UPF entity that currently serves the terminal device. In this way, the terminal device needs to establish a new session for the UPF entity selected again. In the process of establishing the new session, the SMF entity can allocate a new IP address for the terminal device. The new IP address is different from the previously allocated IP address.
[00225] [00225] Furthermore, it can be learned from the previous description of the method to obtain the condition of use information that, when the changed IP address of the terminal device is one of the IP addresses indicated by the defined information, the location of the terminal device is still it will be within the area range corresponding to the defined information. Therefore, the application server corresponding to the domain name obtained by the DNS server through the resolution in S302 may still be the most suitable application server. For example, the application server is still closer to the terminal device. In this way, the terminal device can continue to perform data transmission with the application server based on the application server's IP address. When the changed IP address of the terminal device is not included in the IP addresses indicated by the defined information, for example, the application server corresponding to the domain name obtained by the DNS server through the resolution in S302 can no longer be closer to the terminal device. To ensure the efficient communication of accessing the domain name through the terminal device, the terminal device must re-perform DNS resolution on the domain name.
[00226] [00226] Optionally, after receiving the reply message from the DNS server, the terminal device can generate a DNS caching record, and temporarily store the DNS caching record. The DNS caching record includes the domain name, condition of use information, and the IP address of the application server.
[00227] [00227] According to the method, the terminal device temporarily caches the DNS caching record locally, and when the terminal device additionally needs to access the domain name subsequently, the terminal device can quickly obtain, based on the DNS caching temporarily stored, the application server IP address through resolution, thereby improving the efficiency of domain name resolution, reducing latency of access to the domain name, and reducing the transmission of various related messages when the terminal device perform DNS resolution.
[00228] [00228] Optionally, the DNS caching record generated by the terminal device additionally includes TTL lifetime of the DNS caching record. The TTL can be obtained by the terminal device from the reply message.
[00229] [00229] Due to the fact that the DNS caching record is valid within the TTL, in the process in which the terminal device executes S304, when determining that the IP address of the terminal device or the location of the terminal device are changed within of the TTL, the terminal device determines whether the terminal device from which the information is changed satisfies the condition indicated by the condition of use information. In this way, when the terminal device from which the information is changed still satisfies the condition indicated by the usage condition information, the terminal device can continue to perform data transmission with the application server based on the application server's IP address. in the DNS caching record.
[00230] [00230] According to the method provided in this embodiment of this request, the DNS server performs the resolution on the domain name requested by the terminal device, and then sends, to the terminal device, the IP address of the application server corresponding to the domain name obtained through the resolution and the condition of use information indicating the condition that will be satisfied when the terminal device can access the domain name using the IP address of the application server. In this way, the terminal device can perform, based on the IP address received from the application server, data transmission with the application server, and when the terminal device information is changed due to the movement of the terminal device and the terminal device does not more satisfies the condition indicated by the condition of use information, the terminal device may re-execute DNS resolution on the domain name. When the terminal device information is changed and the terminal device no longer satisfies the condition indicated by the usage condition information, the application server previously obtained through the resolution may no longer be the application server that is the most suitable for the device terminal. In this case, according to the solution, the terminal device can obtain another suitable application server by re-executing the DNS resolution on the domain name. For this reason, in the solution, the communication efficiency of the terminal device can be improved, avoiding the waste of resources in a communications system.
[00231] [00231] Based on the domain name access method provided in the embodiment shown in Figure 3, an embodiment of this request additionally provides an example of the domain name access method. The example is applied to the communications system shown in Figure 1. With reference to Figures 4A and 4B, an example procedure includes the following steps:
[00232] [00232] S401: A terminal device establishes a PDU 1 session through network element devices (an AMF entity, an SMF entity and an UPF 1 entity) on a central network and an AN 1 device. a PDU 1 session, an UPF entity anchor (anchor) selected by the SMF entity is the UPF 1 entity. Therefore, the UPF 1 entity participates in the PDU 1 session establishment procedure.
[00233] [00233] In the procedure for establishing a PDU 1 session, the SMF entity allocates an IP address 1 for the terminal device.
[00234] [00234] S402: After successfully establishing the PDU 1 session, the terminal device sends, via the AN 1 device and the UPF 1 entity when the terminal device needs to access a domain name, a message requesting a name resolution request. domain that leads the domain name to a DNS server.
[00235] [00235] The domain name resolution request message carries location information 1 of the terminal device or an IP address 1 of the terminal device.
[00236] [00236] S403: The DNS server performs the resolution on the domain name to obtain an IP address of an application server 1 corresponding to the domain name, and determines the defined information 1 based on the location information 1 of the terminal device or the IP address 1 of the terminal device conducted in the domain name resolution request message.
[00237] [00237] The information defined 1 indicates at least one IP address of the terminal device.
[00238] [00238] For a way in which the DNS server determines the defined information 1 based on the location information 1 of the terminal device or the IP address 1 of the terminal device, refer to the description of S303 in Figure 3. Details will not be described here again.
[00239] [00239] S404: The DNS server sends a domain name resolution reply message to the terminal device via the UPF 1 entity and the AN 1 device. The domain name resolution reply message includes the IP address of the server application 1 and the defined information 1.
[00240] [00240] S405: The DNS server generates and temporarily stores a DNS 1 caching record. The DNS 1 caching record includes the domain name, the defined information 1, and the IP address of the application server 1.
[00241] [00241] S406: After receiving the domain name resolution reply message, the terminal device generates and temporarily stores the DNS 1 caching record.
[00242] [00242] The DNS 1 caching record generated by the terminal device includes the same content as the DNS 1 caching record generated by the DNS server.
[00243] [00243] Optionally, the DNS 1 caching record can additionally include TTL from the DNS 1 caching record. The TTL can be notified by the DNS server to the terminal device using the domain name resolution reply message on S404. Optionally, when the DNS 1 caching record includes the TTL, the terminal device and the DNS server can temporarily store the DNS 1 caching record synchronously. In this way, a period of time during which the DNS 1 caching record is stored on the terminal device completely overlaps with a period of time during which the DNS 1 caching record is stored on the DNS server.
[00244] [00244] After S404, the terminal device can perform, based on the IP address obtained from the application server 1 and the IP address 1 obtained from the terminal device, data transmission with the application server 1. As shown in the figure, through the AN 1 device and the UPF entity 1, the terminal device can send uplink data to application server 1 and receive downlink data sent by application server 1.
[00245] [00245] S407. The SMF entity determines that it is required again to select an anchor UPF entity for the terminal device.
[00246] [00246] Optionally, when the location of the terminal device moves (the terminal device accesses an AN 2 device), the SMF entity will determine, based on the real-time location information 2 of the terminal device, that it is required again to select the entity UPF anchor for the terminal device. Alternatively, the SMF entity can determine, based on a UPF 1 entity's load status, that it is required to select the anchor UPF entity again.
[00247] [00247] S408: The SMF sends a NAS message to the terminal device, to instruct the terminal device to reestablish a PDU session.
[00248] [00248] S409: Similar to S401, the terminal device establishes a PDU 2 session through network element devices in the central network and the AN 2 device. In a procedure for establishing a PDU 2 session, the anchor UPF entity selected by the entity SMF is an UPF 2 entity. Therefore, the UPF 2 entity participates in the procedure for establishing a PDU 2 session.
[00249] [00249] In the procedure for establishing a PDU 2 session, the SMF entity allocates an IP address 2 for the terminal device.
[00250] [00250] S410: When determining that the terminal device's IP address is changed, the terminal device will determine whether the changed IP address (IP address 2) of the terminal device is included in at least one IP address indicated by the defined information 1 .
[00251] [00251] When determining that the changed IP address of the terminal device is not included in at least one IP address indicated by the information defined 1, the terminal device will re-execute the DNS resolution in the domain name, that is, it will send again, through the AN 2 device and UPF 2 entity, a domain name resolution request message that drives the domain name of the DNS server.
[00252] [00252] The domain name resolution request message leads to the location information 2 of the terminal device or the IP address 2 of the terminal device.
[00253] [00253] S411: The DNS server reruns the resolution on the domain name, to obtain an IP address of an application server 2 corresponding to the domain name, and determines the defined information 2 based on the location information of the terminal device or the IP address 2 of the terminal device conducted in the recently received domain name resolution request message.
[00254] [00254] The information defined 2 indicates at least one IP address of the terminal device.
[00255] [00255] Similarly, for a way in which the DNS server determines the defined information 2 based on the location information 2 of the terminal device or the IP address 2 of the terminal device, refer to the description of step S303 in Figure 3. details are not described again here.
[00256] [00256] S412: The DNS server sends a domain name resolution reply message to the terminal device via the UPF 2 entity and the AN 2 device. The domain name resolution reply message includes the server's IP address application 2 and the defined information 2.
[00257] [00257] S413: The DNS server generates and temporarily stores a DNS caching record 2. The DNS caching record 2 includes the domain name, the defined information 2, and the IP address of the application server 2.
[00258] [00258] S414: After receiving the domain name resolution reply message, the terminal device generates and temporarily stores the DNS 2 caching record.
[00259] [00259] The DNS 2 caching record generated by the terminal device includes the same content as the DNS 2 caching record generated by the DNS server.
[00260] [00260] After S414, the terminal device can execute, based on the IP address obtained from the application server 2 and the IP address 2 obtained from the terminal device, the data transmission with the application server 2. As shown in the figure, through from the AN 2 device and the UPF entity 2, the end device can send uplink data to application server 2 and receive downlink data sent by application server 2.
[00261] [00261] In the previous example, the DNS server performs the resolution on the domain name requested by the terminal device, and then sends, to the terminal device, the IP address of the application server corresponding to the domain name obtained through the resolution and the information defined indicating at least one IP address of the terminal device. In this way, the terminal device can perform, based on the IP address received from the application server, data transmission with the application server, and when the IP address of the terminal device is changed and the changed IP address is not included in at least at least one IP address indicated by the defined information, the terminal device can re-execute DNS resolution on the domain name. Due to the mobility of the terminal device, when the changed IP address of the terminal device is not included in at least one IP address, the application server previously obtained through the resolution will no longer be the application server that is the most suitable for the terminal device . In this case, according to the method in the example above, the terminal device can obtain the IP address of another suitable application server by re-executing the DNS resolution in the domain name, thus executing the data transmission with the application server. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system is also avoided.
[00262] [00262] It will be noted that Figures 4A and 4B show an example of domain name access when the condition of use information includes the defined information. For an example of domain name access when condition of use information includes location range information and an example of domain name access when condition of use information includes defined information and location range information , refer to Figures 4A and 4B. The details are not described again in this order.
[00263] [00263] One embodiment of this request provides another domain name access method, applied to the communications system shown in Figure 1. With reference to Figure 5, a method procedure includes the following steps.
[00264] [00264] S501: In a procedure of establishing a first session by means of a terminal device, an SMF entity obtains a first domain name from a DNS server in a first DN accessed by the terminal device.
[00265] [00265] The first domain name includes a domain name corresponding to the application server included in the first DN. For example, the first domain name includes all domain names corresponding to all application servers included in the first DN.
[00266] [00266] Optionally, the SMF entity can obtain, from a PCF entity or an NEF entity in a communications system, the first domain name of the application server in the first DN.
[00267] [00267] After S501, through an UPF entity anchor determined in the procedure of establishing the first session, the terminal device can request a DNS server to perform the resolution on a destination domain name (included in the first domain name) required to be accessed, and perform data transmission with an application server corresponding to the destination domain name in the first DN after the resolution is successful.
[00268] [00268] S502: In a procedure of establishing a second session by the terminal device, the SMF entity obtains a second domain name from an application server in a second DN accessed by the terminal device.
[00269] [00269] Similar to S501, the SMF entity can alternatively obtain, from the PCF entity or the NEF entity, the second domain name of the application server in the second DN.
[00270] [00270] The second domain name includes a domain name corresponding to the application server included in the second DN. For example, the second domain name includes all domain names corresponding to all application servers included in the second DN.
[00271] [00271] The first DN and the second DN are different area networks. Due to the mobility of the terminal device, when the terminal device is moved after S501, when the second DN is closer to the terminal device than the first DN, the terminal device will access the second DN that is closest to the terminal device to save the network resources. Therefore, the terminal device needs to access the second DN with the establishment of the second session.
[00272] [00272] Because each area network generally includes at least one application server and each application server corresponds to a corresponding domain name, the first domain name and second domain name respectively include at least one domain name. domain.
[00273] [00273] In addition, an application server corresponding to the same domain name can be deployed in different DNs. In this way, the terminal device can access the same domain name in different DNs.
[00274] [00274] S503: When the first domain name and the second domain name include the same domain name, the SMF entity will send indication information to the terminal device. Referral information is used to instruct the terminal device to perform DNS resolution on the domain name.
[00275] [00275] When the first domain name is completely different from the second domain name, there will be no server corresponding to the destination domain name in the second DN. Therefore, the terminal device must continue to perform data transmission with the application server on the first DN to access the destination domain name.
[00276] [00276] When both the first domain name and the second domain name include the destination domain name, it can be learned from previous descriptions that the distance between the second DN and the terminal device is less than the distance between the first DN and the terminal device, that is, the terminal device is closest to the application server in the second DN. Therefore, as compared to the way in which the terminal device performs data transmission with the application server on the first DN to access the destination domain name, in the way in which the terminal device performs data transmission with the server of application in the second DN to access the destination domain name, the communication efficiency of the terminal device is improved, and transmission resources in the communications system are saved.
[00277] [00277] Scenario 1: The SMF entity cannot determine the destination domain name that was accessed by the terminal device after the terminal device accesses the first DN.
[00278] [00278] In scenario 1, the SMF entity determines, determining whether the first domain name and the second domain name include the same domain name, whether it is necessary to send the referral information.
[00279] [00279] Optionally, that the first domain name and the second domain name include the same domain name includes any of the following three cases.
[00280] [00280] First case: The first domain name is completely the same as the second domain name (the first domain name and the second domain name have the same number of domain names and the same domain names). For example, the first domain name includes Baidu and Sina, and the second domain name includes Baidu and Sina.
[00281] [00281] Second case: Each domain name in the first domain name is included in the second domain name (the number of domain names included in the second domain name is greater than the number of domain names included in the first domain name domain). For example, the first domain name includes Baidu and Sina, and the second domain name includes Baidu, Sina and Tencent.
[00282] [00282] Third case: the first domain name and the second domain name include at least the same domain name. In other words, some domain names in the first domain name are included in the second domain name. For example, the first domain name includes Baidu and Sina, and the second domain name includes Sina and Tencent.
[00283] [00283] In the first case and in the second case, the second domain name definitely includes the destination domain name that was accessed by the terminal device when the terminal device accesses the first DN. However, in the third case, the second domain name can include the destination domain name. Therefore, in the first case and in the second case, the SMF entity sends the referral information to the terminal device, and the terminal device communicates with the application server on the second DN to access the destination domain name. Therefore, in the method, the communication efficiency of the terminal device can be improved, and the transmission resources in the communications system can be saved. However, in the previous third case, the SMF entity sends the referral information to the terminal device, and the terminal device can communicate with the application server on the second DN, to access the destination domain name. In the method, the communication efficiency of the terminal device can be improved.
[00284] [00284] In a possible implementation of scenario 1, the referral information does not include any domain name. In this way, referral information can instruct the terminal device to perform DNS resolution on the domain name accessed by the terminal device after the terminal device accesses the first DN, or instruct the terminal device to perform DNS resolution on all domain names. domain currently accessed by the terminal device.
[00285] [00285] In another possible implementation of scenario 1, the referral information additionally includes the first domain name (or the second domain name). In this way, the referral information can instruct the terminal device to perform DNS resolution on the domain name that is currently accessed by the terminal device and that is in the first domain name (or the second domain name).
[00286] [00286] Scenario 2: The SMF entity can determine the destination domain name that was accessed by the terminal device after the terminal device accesses the first DN.
[00287] [00287] In scenario 2, when the first domain name and second domain name determined by the SMF entity in S503 include the destination domain name, the SMF entity will send the indication information to the terminal device.
[00288] [00288] In a possible implementation of scenario 2, the referral information includes the destination domain name. In this way, the indication information can instruct the terminal device to execute the resolution in the destination domain name, thus improving the pertinence of the indication information and additionally solving the problem of wasting resources.
[00289] [00289] S504: After receiving the indication information, the terminal device performs DNS resolution on the domain name.
[00290] [00290] Optionally, the domain name can be the domain name accessed by the terminal device after the terminal device accesses the first DN, or the domain name currently accessed by the terminal device, or the domain name in the first domain name (or the second domain name) currently accessed by the terminal device, or the destination domain name notified by the SMF entity using referral information.
[00291] [00291] Optionally, for a process in which the terminal device performs DN resolution on the domain name, refer to the procedure of the domain name access method shown in Figure 3 or in Figures 4A and 4B. The details are not described here again.
[00292] [00292] According to the method provided in this embodiment of this request, when determining that the second domain name in the second DN currently accessed by the terminal device includes the same domain name as the first domain name in the first DN previously accessed by the end device, the SMF entity will instruct the end device to rerun DNS resolution on the domain name. In this way, the terminal device will be able to rerun DNS resolution on the domain name to obtain a suitable application server on the second DN, and then perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in the communications system can also be avoided;
[00293] [00293] Based on the domain name access method provided in the embodiment shown in Figure 5, an embodiment of this request additionally provides an example of the domain name access method. The example is applied to the communications system shown in Figure 1. With reference to Figures 6A and 6B, an example procedure includes the following steps.
[00294] [00294] S601: When a terminal device requests access to a first DN, the terminal device will establish a PDU 1 session through the network element devices (an AMF entity, an SMF entity, and an anchor UPF entity selected by the SMF entity - a UPF entity 1) on a central network and an AN 1 device. In the procedure for establishing the PDU 1 session, the SMF entity obtains a first domain name from an application server in the first DN.
[00295] [00295] In the procedure for establishing a PDU 1 session, the SMF entity allocates an IP address 1 for the terminal device.
[00296] [00296] Optionally, the entity can obtain the first domain name of a PCF entity in the communications system. For example, in the session establishment procedure shown in Figures 2A and 2B, the SMF entity can obtain the first domain name of the PCF entity in the process of executing S206 or S208. Alternatively, the SMF entity can obtain the first domain name from an NEF entity. For example, the SMF entity can obtain the first domain name of the NEF entity in a process of obtaining subscription data.
[00297] [00297] S602: After successfully establishing the PDU 1 session, the terminal device sends, via the AN 1 device and the UPF 1 entity when the terminal device needs to access an application server corresponding to a domain name, a message from domain name resolution request by conducting the domain name to a DNS server.
[00298] [00298] S603: The DNS server performs the resolution on the domain name to obtain an IP address of an application server 1 in the first DN corresponding to the domain name.
[00299] [00299] Optionally, the DNS server may alternatively determine, based on the location information 1 of the terminal device or the IP address 1 of the terminal device conducted in the domain name resolution request message, the condition of use information 1 of the application server IP address 1. For the specific process, refer to the description of S303 in Figure 3. The details will not be described here again.
[00300] [00300] S604. The DNS server sends a domain name resolution reply message to the terminal device through the UPF entity 1 and the AN 1 device. The domain name resolution reply message includes the IP address of application server 1.
[00301] [00301] Optionally, the domain name resolution reply message additionally includes the condition of use information 1.
[00302] [00302] S605: The DNS server generates and temporarily stores a DNS 1 caching record. The DNS 1 caching record includes the domain name and IP address of the application server 1.
[00303] [00303] Optionally, the caching record
[00304] [00304] S606: After receiving the domain name resolution reply message, the terminal device generates and temporarily stores the DNS 1 caching record.
[00305] [00305] The DNS 1 caching record generated by the terminal device includes the same content as the DNS 1 caching record generated by the DNS server.
[00306] [00306] Optionally, the DNS 1 caching record can additionally include TTL from the DNS 1 caching record. The TTL can be notified by the DNS server to the terminal device using the domain name resolution reply message on S604. Optionally, when the DNS 1 caching record includes the TTL, the terminal device and the DNS server can temporarily store the DNS 1 caching record synchronously. In this way, a period of time during which the DNS 1 caching record is stored on the terminal device completely overlaps with a period of time during which the DNS 1 caching record is stored on the DNS server.
[00307] [00307] After S604, the terminal device can execute, based on the IP address obtained from the application server 1 and the IP address 1 obtained from the terminal device, the data transmission with the application server 1. As shown in the figure, through the AN 1 device and the UPF entity 1, the terminal device can send uplink data to application server 1 and receive downlink data sent by application server 1.
[00308] [00308] S607: The SMF entity determines that it is necessary to select an UPF anchor entity for the terminal device again.
[00309] [00309] Optionally, when a location of the terminal device moves (the terminal device accesses an AN 2 device, for example, the terminal device moves near a second ND), the terminal device can determine, based on the location information real-time 2 from the terminal device, which is again required to select the anchor UPF entity for the terminal device. Alternatively, the SMF entity can determine, based on a UPF 1 entity's load status, that it is required again to select the anchor UPF entity.
[00310] [00310] S608: The SMF sends a NAS message to the terminal device, to instruct the terminal device to reestablish a PDU session.
[00311] [00311] S609: Similar to S601, the terminal device establishes a PDU 2 session through the network element devices (the AMF entity, the SMF entity, and an anchor UPF entity selected by the SMF entity - an UPF 2 entity) on the network central and on the AN device 2. In the procedure for establishing the PDU 2 session, the SMF entity obtains a domain name from an application server on the second DN.
[00312] [00312] In the procedure for establishing the PDU 2 session, the SMF entity allocates an IP address 2 for the terminal device.
[00313] [00313] S610: When determining that the first domain name and the second domain name include the same domain name, the SMF entity sends the indication information to the terminal device. Referral information is used to instruct the terminal device to perform DNS resolution on a domain name currently accessed by the terminal device.
[00314] [00314] For step S610, refer to the description of S503 in Figure 5. The details will not be described here again.
[00315] [00315] S611: After receiving the indication information, the terminal device re-executes DNS resolution on the domain name, that is, it resends, via the AN 2 device and the UPF 2 entity, a message requesting the resolution of the name of domain that conducts the domain name to the DNS server.
[00316] [00316] S612: The DNS server reruns the resolution on the domain name, to obtain an IP address of a DNS 2 server on the second DN corresponding to the domain name.
[00317] [00317] Optionally, the DNS server may alternatively determine, based on the location information 2 of the terminal device or an IP address 2 of the terminal device conducted in the recently received domain name resolution request message, the condition of use information 2 of the IP address of the application server 2. For the specific process, refer to the description of S303 in Figure 3. The details will not be described here again.
[00318] [00318] S613: The DNS server sends a domain name resolution reply message to the terminal device via the UP 2 entity of the AN 2 device. The domain name resolution reply message includes the IP address of the application 2.
[00319] [00319] Optionally, the domain name resolution reply message additionally includes the condition of use information 2.
[00320] [00320] S614: The DNS server generates and temporarily stores a DNS 2 caching record. The DNS 2 caching record includes the domain name and IP address of the application server 2.
[00321] [00321] Optionally, the DNS 2 caching record additionally includes the condition of use information.
[00322] [00322] S615: After receiving the domain name resolution reply message, the terminal device generates and temporarily stores the DNS 2 caching record.
[00323] [00323] The DNS 2 caching record generated by the terminal device includes the same content as the DNS 2 caching record generated by the DNS server.
[00324] [00324] After S613, the terminal device can perform, based on the IP address obtained from the application server 2 and the IP address 2 obtained from the terminal device, data transmission with the application server 2. As shown in the figure, through the AN 2 device and the UPF entity 2, the terminal device can send uplink data to application server 2 and receive downlink data sent by application server 2.
[00325] [00325] In the previous example, when determining that the second domain name in the second DN currently accessed by the terminal device includes the same domain name as the first domain name in the first DN previously accessed by the terminal device, the SMF entity instructs the terminal device to re-perform DNS resolution on the domain name. In this way, the terminal device can rerun DNS resolution on the domain name to obtain a more suitable application server on the second DN, and then perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in the communications system can also be avoided.
[00326] [00326] One embodiment of this request provides yet another domain name access method applied to the communications system shown in Figure 1. With reference to Figure 7, a method procedure includes the following steps.
[00327] [00327] S701: An NEF entity determines that the IP address information of an application server corresponding to a domain name is changed.
[00328] [00328] The IP address information of the application server is a data network access identifier (DNAI) of the application server. The application server's DNAI can be used to indicate an application server location.
[00329] [00329] The NEF entity stores a correspondence between the domain name and the IP address information of the application server.
[00330] [00330] Due to the fact that the application server generally needs to interact with a PCF entity through the NEF entity, in the process of interaction between the application server and the PCF entity, the NEF entity converts an IP address from the application server to the DNAI of the application server, thus generating the correspondence between the domain name and the DNAI of the application server.
[00331] [00331] For example, when the application server sends an application function traffic steering request request message to the PCF entity through the NEF entity, the NEF entity can determine the DNAI of the application server application based on the application server's IP address, determine the domain name corresponding to the application server, generate the correspondence between the domain name and the application server's DNAI, and store the correspondence. Optionally, when the end device moves to a location range to which a DN belongs in which the application server is located, the application server can be triggered to send the application function traffic targeting message.
[00332] [00332] When an NEF entity previously stores a match between the domain name and a DNAI of another application server, the NEF entity will replace the match with the newly generated match between the domain name and the DNAI of the application server. In this case, the NEF entity can determine that the application server's DNAI corresponding to the domain name is changed.
[00333] [00333] S702: The NEF entity notifies the PCF entity that the application server's IP address information corresponding to the domain name is changed.
[00334] [00334] Optionally, the NEF entity sends an IP address information change notification message to the PCF entity, to notify the PCF entity that the application server's IP address information corresponding to the domain name is changed.
[00335] [00335] S703: The PCF entity learns, from the NEF entity, that the application server's IP address information corresponding to the domain name is changed, and then sends the referral information to the SMF entity. Referral information is used to instruct the SMF entity to notify, when an IP address allocated by the SMF entity to the terminal device is changed, the terminal device to perform DNS resolution on the domain name.
[00336] [00336] A change in the DNAI corresponding to the domain name in the NEF entity indicates the addition of an application server corresponding to the domain name to a communications system. When the IP address is changed due to movement of the terminal device, the application server closest to the terminal device can also be changed (which can be changed to an application server to which the updated DNAI corresponding to the domain name belongs). Therefore, it is required to instruct the SMF entity via S703 to notify, when the IP address allocated by the SMF entity to the terminal device is changed, the terminal device to perform DNS resolution on the domain name.
[00337] [00337] A change in the DNAI corresponding to the domain name in the NEF entity indicates the addition of an application server corresponding to the domain name to a communications system. When the IP address is changed due to movement of the terminal device, the application server closest to the terminal device can also be changed (which can be changed to an application server to which the updated DNAI corresponding to the domain name belongs). Therefore, it is required to instruct the SMF entity via S703 to notify, when the IP address allocated by the SMF entity to the terminal device is changed, the terminal device to re-execute DNS resolution on the domain name.
[00338] [00338] The application server obtained each time through resolution by the DNS server for the terminal device is closest to (most suitable for) the terminal device, and when the IP address of the terminal device is not changed, no relatively large changes will occur the location of the terminal device. Therefore, the application server corresponding to the domain name previously obtained through the DNS resolution should still be more likely to be the application server closest to the terminal device, and no DNS resolution needs to be re-executed on the domain name. Conversely, when the IP address of the terminal device is changed, it will indicate that a relatively large change has occurred in the location of the terminal device. The application server corresponding to the domain name previously obtained through DNS resolution is no longer likely to be the application server closest to the terminal device. Therefore, DNS resolution needs to be re-performed on the domain name to obtain another more suitable application server, thus ensuring the communication efficiency of the terminal device and preventing the waste of transmission resources.
[00339] [00339] Optionally, in this embodiment of this request, the indication information can additionally be used to instruct the SMF entity to reconfigure a terminal device user plan, to initiate a procedure for reallocating the IP address to the terminal device.
[00340] [00340] S704: After receiving the indication information from the PCF entity, the SMF entity notifies, based on the indication information when the IP address allocated by the SMF entity to the terminal device is changed, the terminal device executing DNS resolution in the domain name.
[00341] [00341] Optionally, the SMF entity can send the indication of resolution information to the terminal device, to notify the terminal device to re-execute DNS resolution on the domain name.
[00342] [00342] S705: After learning from the SMF entity that DNS resolution needs to be performed on the domain name, the terminal device performs DNS resolution on the domain name.
[00343] [00343] Optionally, for a process in which the terminal device performs DNS resolution on the domain name, refer to the procedure for the domain name access method shown in Figure 3 or in Figures 4A and 4B. The details will not be described here again.
[00344] [00344] According to the method provided in this embodiment of this request, after determining that the application server's IP address information corresponding to the domain name is changed, the NEF entity instructs, through the PCF entity, the SMF entity to notify , when the IP address allocated by the SMF entity to the terminal device is changed, the terminal device to re-perform DNS resolution on the domain name. In this way, the terminal device will be able to obtain a more suitable application server with the resolution reexecution, and additionally perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of the transmission resources of the communications system can also be avoided.
[00345] [00345] Based on the domain name access method provided in the embodiment shown in Figure 7, an embodiment of this request additionally provides an example of the domain name access method. The example is applied to the communications system shown in Figure 1. An NEF entity in the communications system can store a match between a domain name and an application server's IP address information. With reference to Figures 8A, 8B and 8C, an example procedure includes the following steps.
[00346] [00346] S801: a terminal device establishes a PDU 1 session through the network element devices (an AMF entity, an SMF entity, an anchor UPF entity selected by the SMF entity - an UPF 1 entity, and a PCF entity) in a central network and an AN 1 device.
[00347] [00347] In the procedure for establishing the PDU 1 session, the SMF entity allocates an IP address 1 for the terminal device.
[00348] [00348] S802: After successfully establishing the PDU 1 session, the terminal device sends, through the AN 1 device and the UPF 1 entity when the terminal device needs to access a domain name, a message requesting a name resolution request. domain by conducting the domain name to a DNS server.
[00349] [00349] S803: The DNS server performs a resolution on the domain name to obtain an IP address of an application server 1 corresponding to the domain name.
[00350] [00350] Due to the fact that an application server's DNAI corresponding to the domain name stored in the NEF entity is an application server 1's DNAI, the DNS server obtains application server 1 corresponding to the domain name through resolution.
[00351] [00351] Optionally, the DNS server may alternatively determine, based on the location information 1 of the terminal device or an IP address 1 of the terminal device conducted in the domain name resolution request message, the condition of use information 1 application server 1. For a specific process, refer to the description of S303 in Figure 3. The details will not be described here again.
[00352] [00352] S804: The DNS server sends a domain name resolution reply message to the terminal device through the UP 1 entity of the AN 1 device. The domain name resolution reply message includes the IP address of the application 1.
[00353] [00353] Optionally, the domain name resolution reply message additionally includes the condition of use information 1.
[00354] [00354] S805: The DNS server generates and temporarily stores a DNS 1 caching record. The DNS 1 caching record includes the domain name and IP address of the application server 1.
[00355] [00355] Optionally, the DNS 1 caching record additionally includes usage condition information 1.
[00356] [00356] S806: After receiving the domain name resolution reply message, the terminal device generates and temporarily stores the DNS 1 caching record.
[00357] [00357] The DNS 1 caching record generated by the terminal device includes the same content as the DNS 1 caching record generated by the DNS server.
[00358] [00358] Optionally, the DNS caching record 1 can include TTL from the DNS caching record
[00359] [00359] After S804, the terminal device can execute, based on the IP address obtained from the application server 1 and the IP address 1 obtained from the terminal device, the data transmission with the application server 1. As shown in the figure, through the AN 1 device and the UPF entity 1, the terminal device can send uplink data to application server 1 and receive downlink data sent by application server 1.
[00360] [00360] S807: An application server 2 corresponding to the domain name sends an application function traffic steering request request message to the PCF entity through an NEF entity. The NEF entity forwards the application function traffic routing request message to the PCF entity.
[00361] [00361] S808: The PCF entity returns a response message directing traffic from application function to application server 2 through the NEF entity.
[00362] [00362] S809. When forwarding the application function traffic routing request message, the NEF entity will obtain an IP address from application server 2, convert the IP address of application server 2 into a DNAI of application server 2, and generate and will store a match between the domain name and the application server 2's DNAI. Due to the fact that the application server's DNAI corresponding to the domain name stored in the NEF entity is changed from the application server 1's DNAI to the DNAI from application server 2, the NEF entity determines that the application server's IP address information corresponding to the domain name is changed, and sends an IP address information change notification message to the PCF entity to notify the PCF entity that the application server's IP address information corresponding to the domain name is changed.
[00363] [00363] S810: The PCF entity triggers the SMF entity to update a session PCC rule, and sends the referral information to the SMF entity. Referral information is used to instruct the SMF entity to notify, when an IP address allocated by the SMF entity to the terminal device is changed, the terminal device to perform DNS resolution on the domain name.
[00364] [00364] For example, the PCF entity sends an update notification of session management policy control to the SMF entity. The session management policy control update notification includes referral information.
[00365] [00365] S811: The SMF entity initiates a user device reconfiguration procedure for the terminal device, and an anchor UPF entity again selected for the terminal device in the user plan reconfiguration procedure is an UPF 2 entity.
[00366] [00366] S812: The SMF entity reallocates an IP address, that is, an IP address 2, to the terminal device.
[00367] [00367] S813: The SMF entity notifies, through the NEF entity, the application server 2 that the session target DNAI information is the application server 2 DNAI.
[00368] [00368] S814: When determining that the IP address allocated to the terminal device is changed, the SMF entity sends the resolution indication information to the terminal device via the AMF entity, to notify the terminal device to perform DNS resolution in the domain name.
[00369] [00369] S815: After receiving the indication of resolution information, the terminal device re-executes DNS resolution on the domain name, that is, it resends, through the AN 2 device and the UPF 2 entity, a message requesting resolution of domain name that leads the domain name to the DNS server.
[00370] [00370] S816: The DNS server reruns the resolution on the domain name, to obtain the IP address of application server 2 corresponding to the domain name.
[00371] [00371] Optionally, the DNS server may alternatively determine, based on the location information 2 of the terminal device or an IP address 2 of the terminal device conducted in the recently received domain name resolution request message, the domain condition information. use 2 of application server IP address 2.
[00372] [00372] S817: The DNS server sends a domain name resolution reply message to the terminal device through the UPF 2 entity and the AN 2 device. The domain name resolution reply message includes the server's IP address application 2.
[00373] [00373] Optionally, the domain name resolution reply message additionally includes the condition of use information 2.
[00374] [00374] S818. The DNS server generates and temporarily stores a DNS 2 caching record. The DNS 2 caching record includes the domain name and IP address of the application server 2.
[00375] [00375] Optionally, the DNS 2 caching record additionally includes usage condition information 2.
[00376] [00376] S819: After receiving the domain name resolution reply message, the terminal device generates and temporarily stores the DNS 2 caching record.
[00377] [00377] The DNS caching record generated by the terminal device includes the same content as the DNS 2 caching record generated by the DNS server.
[00378] [00378] After S817, the terminal device can perform, based on the IP address obtained from the application server 2 and the IP address 2 obtained from the terminal device, data transmission with the application server 2. As shown in figure 2 , through the AN 2 device and the UPF entity 2, the terminal device can send uplink data to application server 2 and receive downlink data sent by application server 2.
[00379] [00379] In the previous example, after determining that the application server's IP address information corresponding to the domain name is changed, the NEF entity instructs, through the PCF entity, the SMF entity to notify, when the IP address allocated by the SMF entity for the terminal device is changed, the terminal device to rerun DNS resolution on the domain name. In this way, the terminal device can obtain a more suitable application server with the re-execution of the DNS resolution, and additionally perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, while also wasting the transmission resources of the communications system.
[00380] [00380] It will be noted that each message of each figure in the embodiments of this request may have another name. In addition, the information between the network elements can alternatively be transferred by invoking the network functions of the network elements in a service-based architecture. This is not limited to the fulfillment of this request. The IP address in the previous embodiments can be an IPv4 address or an IPv6 prefix.
[00381] [00381] Furthermore, it will be further noted that the DNS includes a plurality of DNS servers, and the plurality of DNS servers can be distributed in the DNS in a hierarchical architecture. Therefore, in the previous embodiments, a first DNS server that performs DNS resolution on a domain name for the first time can be the same or different from a second DNS server that re-performs DNS resolution on the domain name. When the first DNS server is different from the second DNS server, the first DNS server and the second DNS server can be different DNS servers in the same hierarchy. For example, both the first DNS server and the second DNS server are either local DNS servers or root DNS servers. Alternatively, the first DNS server and the second DNS server are DNS servers in different hierarchies. This is not limited to this order. In the figures corresponding to the previous embodiments, the first DNS server and the second DNS server are seen as the same DNS server for illustrative purposes only. Therefore, the previous embodiments are not a limitation to this request.
[00382] [00382] Based on the previous embodiments, this request additionally provides a DNS server. The DNS server can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 3 or in Figures 4A and 4B. As shown in the Figure, the DNS server 900 includes: a receiving unit 901, a processing unit 902 and a sending unit 903.
[00383] [00383] Receiving unit 901 is configured to receive a request message from a terminal device, where the request message includes a domain name requested by the terminal device.
[00384] [00384] Processing unit 902 is configured to perform resolution on the domain name, to obtain an Internet Protocol IP address from an application server corresponding to the domain name.
[00385] [00385] The sending unit 903 is configured to send a reply message to the terminal device, where the reply message includes the IP address of the application server and the usage condition information, the usage condition information indicating a condition in which the terminal device accesses the domain name using the application server's IP address.
[00386] [00386] Optionally, the condition of use information includes at least one information among the defined information and location range information. The defined information indicates at least one IP address of the terminal device, and the location range information indicates a location range in which the terminal device is located.
[00387] [00387] Optionally, processing unit 902 is additionally configured to:
[00388] [00388] determine the condition of use information based on the request message.
[00389] [00389] Optionally, the request message additionally includes the location information of the terminal device or the IP address of the terminal device.
[00390] [00390] When determining the condition of use information based on the request message, processing unit 902 is specifically configured to:
[00391] [00391] determine the condition of use information based on the location information of the terminal device or the IP address of the terminal device included in the request message.
[00392] [00392] Optionally, the sending unit 903 is additionally configured to:
[00393] [00393] send the indication information to the terminal device, where the indication information is used to instruct the terminal device to perform DNS resolution on the domain name when the terminal device does not satisfy the condition by the condition of use information.
[00394] [00394] This implementation of this request provides a DNS server. The DNS server performs the resolution on the domain name requested by the terminal device, and then sends the DNS server's IP address to the terminal device corresponding to the domain name obtained through the resolution and the condition of use information indicating the condition that will be satisfied when the terminal device can access the domain name using the application server's IP address. In this way, the terminal device can perform, based on the IP address received from the application server, data transmission with the DNS server, and when the terminal device information is changed due to the movement of the terminal device and the terminal device no longer satisfy the condition indicated by the condition of use information, the terminal device may re-execute DNS resolution on the domain name. When the terminal device information is changed and the terminal device no longer satisfies the condition indicated by the usage condition information, the application server previously obtained through the resolution may no longer be the application server that is the most suitable for the device terminal. In this case, according to the solution, the terminal device can obtain another suitable application server by re-executing the DNS resolution on the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system can also be avoided.
[00395] [00395] In addition, the receiving unit 901, processing unit 902 and sending unit 903 on the DNS server 900 can additionally implement another operation or function of the DNS server in the previous method. The details will not be described here again.
[00396] [00396] Based on the previous embodiments, this application additionally provides a terminal device. The terminal device can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 3 and in Figures 4A and 4B. Referring to Figure 10, terminal device 1000 includes a sending unit 1001, a receiving unit 1002 and a processing unit 1003.
[00397] [00397] The sending unit 1001 is configured to send a reply message to a DNS server of the domain name system, where the request message includes a domain name requested by the terminal device.
[00398] [00398] Receiving unit 1002 is configured to receive a response message from the DNS server, where the response message includes an Internet Protocol IP address of an application server and condition of use information, the application server corresponding to the domain name, and the usage condition information indicating a condition in which the terminal device accesses the terminal device using the application server's IP address.
[00399] [00399] Processing unit 1003 is configured to perform DNS resolution on the domain name when the terminal device does not satisfy the condition indicated by the condition of use information.
[00400] [00400] Optionally, the receiving unit 1002 is additionally configured to receive referral information from the DNS server, where referral information is used to instruct the terminal device to perform DNS resolution on the domain name when the terminal device does not satisfy the condition indicated by the condition of use information.
[00401] [00401] The processing unit 1003 is additionally configured to determine, based on the indication information, whether the terminal device satisfies the condition indicated by the condition of use information.
[00402] [00402] Optionally, the condition of use information includes at least one information among the defined information and location range information. The defined information indicates at least one IP address of the terminal device, and the location range information indicates a location range in which the terminal device is located.
[00403] [00403] When the condition of use information includes the defined information, that the terminal device does not satisfy the condition indicated by the condition of use information includes: an IP address of the terminal device is changed and the changed IP address of the terminal device is not included in at least one IP address indicated by the defined information; and / or
[00404] [00404] when the condition of use information includes the location range information, that the terminal device does not satisfy the condition indicated by the condition of use information includes: a location of the terminal device is changed and the changed location of the terminal device is not is within the location range indicated by the location range information.
[00405] [00405] Optionally, processing unit 1003 is additionally configured to:
[00406] [00406] Temporarily storing a DNS caching record after receiving unit 1002 receives the response message from the DNS server, where the DNS caching record includes the domain name, condition of use information, and the IP address of the application server.
[00407] [00407] Optionally, the DNS caching record additionally includes TTL lifetime of the DNS caching record.
[00408] [00408] When determining that the terminal device does not satisfy the condition indicated by the condition of use information, processing unit 1003 will be specifically configured to:
[00409] [00409] determine that the terminal device does not satisfy, within the TTL, the condition indicated by the condition of use information.
[00410] [00410] This embodiment of this request provides a terminal device. The terminal device performs DNS resolution on the domain name, and then obtains the IP address of the application server corresponding to the domain name and the condition of use information indicating the condition that will be satisfied when the terminal device can access the domain name using the application server's IP address. In this way, the terminal device can perform, based on the IP address received from the application server, data transmission with the application server, and when the information on the terminal device is changed due to the movement of the terminal device and the terminal device does not more satisfies the condition indicated by the condition of use information, the terminal device may re-execute DNS resolution on the domain name. When the terminal device information is changed and the terminal device no longer satisfies the condition indicated by the usage condition information, the application server previously obtained through the resolution can no longer be the application server that is the most suitable for the device terminal. In this case, according to the solution, the terminal device will be able to obtain another suitable application server with the re-execution of the DNS resolution in the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system is also avoided.
[00411] [00411] In addition, the sending unit 1001, the receiving unit 1002 and the processing unit 1003 in the terminal device 1000 can additionally implement another operation or function of the terminal device in the previous method. The details will not be described here again.
[00412] [00412] Based on the previous embodiments, this request additionally provides an SMF entity. The SMF entity can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 5 or in Figures 6A and 6B. As shown in Figure 11, the SMF entity 1100 includes: a retrieval unit 1101, a processing unit 1102 and a sending unit 1103.
[00413] [00413] Obtaining unit 1101 is configured to: obtain, in a procedure of establishing a first session by a terminal device, a first domain name of an application server in a DN data network accessed by the terminal device, and obtain , in a procedure of establishing a second session by the terminal device, a second domain name of an application server in a second DN accessed by the terminal device.
[00414] [00414] Processing unit 1102 is configured to send referral information to the terminal device via sending unit 1103 when the first domain name and second domain name include the same domain name, where the referral information is used to instruct the terminal device to perform DNS resolution on the domain name.
[00415] [00415] The sending unit 1103 is configured to send the indication information to the terminal device.
[00416] [00416] Optionally, when obtaining the first domain name of the application server in the first DN, the obtaining unit 1101 will be specifically configured for:
[00417] [00417] obtain, from a PCF policy control function entity or a network exposure function NEF entity, the first domain name of the application server in the first DN.
[00418] [00418] Optionally, the referral information additionally includes the first domain name or the second domain name
[00419] [00419] This fulfillment of this request provides an SMF entity. When determining that the second domain name in the second DN currently accessed by the terminal device includes the same domain name as the first domain name in the first DN previously accessed by the terminal device, the SMF entity will instruct the terminal device to re-execute the resolution DNS on the domain name. In this way, the terminal device can rerun DNS resolution on the domain name to obtain a more suitable application server on the second DN, and then perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, while also wasting the transmission resources of a communications system.
[00420] [00420] Furthermore, the obtaining unit 1101, the processing unit 1102 and the sending unit 1103 in the SMF entity 1100 can additionally implement the other operation or function of the SMF entity in the previous method. The details will not be described here again.
[00421] [00421] Based on the previous embodiments, this request additionally provides an NEF entity. The NEF entity can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 7 or in Figures 8A, 8B and 8C. Referring to Figure 12, the NEF 1200 entity includes a processing unit 1201 and a sending unit 1202.
[00422] [00422] Processing unit 1201 is configured to determine that the Internet Protocol IP address information of an application server corresponding to a domain name is changed.
[00423] [00423] Sending unit 1202 is configured to notify a PCF policy control function entity that the application server's IP address information corresponding to the domain name is changed.
[00424] [00424] Optionally, the application server's IP address information is an access server's DNAI data network access identifier.
[00425] [00425] This fulfillment of this request provides an NEF entity. After determining that the application server's IP address information corresponding to the domain name is changed, the NEF entity instructs, through the PCF entity, the SMF entity to notify, when the IP address allocated by the SMF entity to a terminal device is changed. changed, the terminal device to re-execute DNS resolution on the domain name. In this way, the terminal device can obtain a more suitable application server with the resolution re-execution, and additionally perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system can also be avoided.
[00426] [00426] In addition, the processing unit 1201 and the sending unit 1202 in the NEF entity 1200 can additionally implement another operation or function of the NEF entity in the previous method. The details will not be described here again.
[00427] [00427] Based on the previous embodiments, this request additionally provides a PCF entity. The PCF entity can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 7 or in Figures 8A, 8B and 8C. Referring to Figure 13, the PCF entity 1300 includes a receiving unit 1301 and a sending unit 1302.
[00428] [00428] Receiving unit 1301 is configured to learn, from an NEF network exposure function entity, that the Internet Protocol IP address information of an application server corresponding to a domain name is changed.
[00429] [00429] Sending unit 1302 is configured to send referral information to an SMF session management role entity, where referral information is used to instruct the SMF entity to notify, when an IP address allocated by the SMF entity for the terminal device is changed, the terminal device to perform DNS resolution on the domain name.
[00430] [00430] This fulfillment of this request provides a PCF entity. After learning from the NEF entity that the application server's IP address information corresponding to the domain name is changed, the PCF entity instructs the SMF entity to notify, when the IP address allocated by the SMF entity to the end device is changed, the terminal device to re-execute DNS resolution on the domain name. In this way, the terminal device can obtain a more suitable application server with the resolution re-execution, and additionally perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system is also avoided.
[00431] [00431] In addition, the receiving unit 1301 and the sending unit 1302 in the PCF entity 1300 can additionally implement another operation or function of the PCF entity in the previous method. The details will not be described here again.
[00432] [00432] Based on the previous embodiments, this request additionally provides an SMF entity. The SMF entity can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 7 or in Figures 8A, 8B and 8C. Referring to Figure 14, the SMF entity 1400 includes a receiving unit 1401 and a processing unit 1402.
[00433] [00433] Receiving unit 1401 is configured to receive indication information from a PCF policy control function entity.
[00434] [00434] Processing unit 1402 is configured to notify, based on indication information, when an IP address allocated by the SMF entity to a terminal device is changed, the terminal device performing DNS resolution on the domain name.
[00435] [00435] This fulfillment of this request provides an SMF entity. After determining that the application server's IP address information corresponding to the domain name is changed, the NEF entity instructs, through the PCF entity, the SMF entity to notify, when the IP address allocated by the SMF entity to the end device is changed, the terminal device to re-perform DNS resolution on the domain name, so that the SMF entity can notify, when an IP address allocated by the SMF entity to the terminal device is changed, the terminal device performing DNS resolution on behalf of domain. In this way, the terminal device can obtain a more suitable application server with the resolution re-execution, and additionally perform data transmission with the application server to access the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, thus also avoiding the waste of transmission resources in a communications system.
[00436] [00436] In addition, the receiving unit 1401 and processing unit 1402 in the SMF entity 1400 can additionally implement another operation or function of the SMF entity in the previous method. The details will not be described here again.
[00437] [00437] It will be noted that the division of modules in the implementation of this request is just an example, being a division of function purely logical. There may be another way of dividing during an effective implementation. In addition, the functional units in the embodiments of this application can be integrated into a processing unit, or each of the functional units can exist physically alone, or two or more units can be integrated into one unit. The integrated unit can be implemented in a form of hardware, or it can be implemented in the form of a functional software unit.
[00438] [00438] When the integrated unit is implemented in the form of the functional software unit and sold or used as a stand-alone product, the integrated unit may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of this application essentially, or the part that contributes to the prior art, or all or some of the technical solutions can be implemented in a form of a software product. The computer software product is stored on a storage medium and includes several instructions for instructing a computer device (which can be a personal computer, a server or a network device) or a processor to perform all or some the steps of the methods described in the embodiments of this application. The previous storage medium includes: any medium that can store a program code, such as a USB flash drive, a removable hard disk, a read-only memory (ROM), a random access memory ( Random Access Memory (RAM)), a magnetic disk, or an optical disk.
[00439] [00439] Based on the previous embodiments, one embodiment of this request additionally provides a DNS server. The DNS server can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 3 or in Figures 4A and 4B, and has the role of the DNS 900 server shown in Figure 9. With reference In Figure 15, the DNS server 1500 includes: a communication interface 1501, a processor 1502 and a memory 1502. The communications interface 1501, processor 1502 and memory 1503 are mutually connected.
[00440] [00440] Optionally, communications interface 1501, processor 1502 and memory 1503 are mutually connected using a 1504 bus. Bus 1504 can be a peripheral component interconnect (PCI) bus, a industry standard extended bus (EISA), or similar. The bus can be classified into an address bus, a data bus, a control bus, or the like. For ease of representation, just one thick line is used to represent the bus in Figure 15,
[00441] [00441] The communications interface 1501 is configured to receive and send data to implement communication with another device in the communications system.
[00442] [00442] Processor 1502 is configured to implement the domain name access method provided in the embodiments shown in Figure 3 or in Figures 4A and 4B. For specific details, refer to the descriptions of the previous embodiments. The details will not be described here again.
[00443] [00443] Memory 1503 is configured to store a program instruction and the like. Specifically, the program statement can include program code. The program code includes a computer operating instruction. Memory 1503 may include a random access memory (RAM), or it may additionally include a non-volatile memory, for example, at least one magnetic disk memory. The processor 1502 executes the program instruction stored in memory 1503 to implement the previous function, thus implementing the domain name access method provided in the previous embodiments.
[00444] [00444] Based on the previous embodiments, an embodiment of this application additionally provides a terminal device. The terminal device can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 3 or Figures 4A and 4B, and has the function of the terminal device 1000 shown in Figure
[00445] [00445] Optionally, transceiver 1061, processor 1602 and memory 1603 are mutually connected using a 1604 bus. Bus 1604 can be a PCI bus, an EISA bus, or the like. The bus can be classified into an address bus, a data bus, a control bus, or the like. For ease of representation, only a thick line is used to represent the bus in Figure 16, but this does not mean that there is only one bus or only one type of bus.
[00446] [00446] Transceiver 1601 is configured to receive and send data to implement communication with another device in the communications system.
[00447] [00447] Processor 1602 is configured to implement the domain name access method provided in the embodiments shown in Figure 3 and or in Figures 4A and 4B. For specific details, refer to the descriptions of the previous embodiments. The details will not be described here again.
[00448] [00448] Memory 1603 is configured to store a program instruction and the like. Specifically, the program statement can include program code. The program code includes a computer operating instruction. Memory 1603 may include RAM, or it may additionally include non-volatile memory, for example, at least one magnetic disk memory. Processor 1602 executes the program instruction stored in memory 1603 to implement the previous function, thus implementing the domain name access method provided in the previous embodiments.
[00449] [00449] Based on the previous embodiments, one embodiment of this request additionally provides an SMF entity.
[00450] [00450] Optionally, the communications interface 1701, processor 1702 and memory 1703 are mutually connected using a 1704 bus. The 1704 bus can be a PCI bus, an EISA bus, or similar. The bus can be classified into an address bus, a data bus, a control bus, or the like. For ease of representation, only a thick line is used to represent the bus in Figure 17, but this does not mean that there is only one bus or only one type of bus.
[00451] [00451] The communications interface 1701 is configured to receive and send data to implement communication with another device in the communications system.
[00452] [00452] Processor 1702 is configured to implement the domain name access method provided in the embodiments shown in Figure 5 or Figures 6A and 6B. For specific details, refer to the descriptions of the previous embodiments. The details will not be described here again.
[00453] [00453] Memory 1703 is configured to store a program instruction and the like. Specifically, the program statement can include program code. The program code includes a computer operating instruction. Memory 1703 may include RAM, or it may additionally include non-volatile memory, for example, at least one magnetic disk memory. Processor 172 executes the program instruction stored in memory 1703 to implement the previous function, thus implementing the domain name access method provided in the previous embodiments.
[00454] [00454] Based on the previous embodiments, one embodiment of this request additionally provides an NEF entity. The NEF entity can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 7 or in Figures 8A, 8B and 8C, and has the function of the NEF 1200 entity shown in Figure 12. Referring to Figure 18, the NEF 1800 entity includes: a communications interface 1801, a processor 1802 and a memory 1803. The communications interface 1801, processor 1802 and memory 1803 are mutually connected.
[00455] [00455] Optionally, the communications interface 1801, processor 1802 and memory 1803 are mutually connected using a 1804 bus. The 1804 bus can be a PCT bus, an EISA bus, or similar. The bus can be classified into an address bus, a data bus, a control bus, or the like. For ease of representation, only a thick line is used to represent the bus in Figure 18, but this does not mean that there is only one bus or only one type of bus.
[00456] [00456] The communication interface 1801 is configured to receive and send data to implement communication with another device in the communications system.
[00457] [00457] Processor 1802 is configured to implement the domain name access method provided in the embodiments shown in Figure 7 or Figures 8A, 8B and 8C. For specific details, refer to the descriptions of the previous embodiments. The details will not be described here again.
[00458] [00458] Memory 1803 is configured to store a program instruction and the like. Specifically, the program instruction may include a program code. The program code includes a computer operating instruction. Memory 1803 may include RAM, or it may additionally include non-volatile memory, for example, at least one magnetic disk memory. Processor 1802 executes the program instruction stored in memory 1803 to implement the previous function, thus implementing the domain name access method provided in the previous embodiments.
[00459] [00459] Based on the previous embodiments, one embodiment of this request additionally provides a PCF entity. The PCF entity can be applied to the communications system shown in Figure 1, to implement the domain name access method shown in Figure 7 or in Figures 8A, 8B and 8C, and has the function of the PCF 1300 entity shown in Figure 13 Referring to Figure 19, the PCF 1900 entity includes: a 1901 communications interface, a 1902 processor and a 1903 memory. The 1901 communications interface, the 1902 processor and the 1903 memory are mutually connected.
[00460] [00460] Optionally, the 1901 communications interface, the 1902 processor and the 1903 memory are mutually connected using a 1904 bus. The 1904 bus can be a PCI bus, an EISA bus, or the like. The bus can be classified into an address bus, a data bus, a control bus, or the like. For ease of representation, only a thick line is used to represent the bus in Figure 19, but this does not mean that there is only one bus or only one type of bus.
[00461] [00461] The communications interface 1901 is configured to receive and send data to implement communication with another device in the communications system.
[00462] [00462] The 1902 processor is configured to implement the domain name access method provided in the embodiments shown in Figure 7 or Figures 8A, 8B and 8C. For specific details, refer to the previous descriptions. The details will not be described here again.
[00463] [00463] Memory 1903 is configured to store a program instruction and the like. Specifically, the program statement can include program code. The program code includes a computer operating instruction. The 1903 memory may include a RAM, or it may additionally include a non-volatile memory, for example, at least one magnetic disk memory. Processor 1902 executes the program instruction stored in memory 1903 to implement the previous function, thus implementing the domain name access method provided in the previous embodiments.
[00464] [00464] Based on the previous embodiments, one embodiment of this request additionally provides an SMF entity. The SMF entity can be applied to the communications system shown in Figure 1 to implement the domain name access method shown in Figure 7 or Figures 8A, 8B or 8C, and has the function of the SMF entity 1400 shown in Figure 14. Referring to Figure 20, the SMF 2000 entity includes: a 2001 communications interface, a 2002 processor and a 2003 memory. The 2001 communications interface, 2002 processor and 2003 memory are mutually connected.
[00465] [00465] Optionally, the communications interface 2201, processor 2002 and memory 2003 are mutually connected using a 2004 bus. The 2004 bus can be a PCI bus, an EISA bus, or similar. The bus can be classified into an address bus, a data bus, a control bus, or the like. For ease of representation, only a thick line is used to represent the bus in Figure 20, but this does not mean that there is only one bus or only one type of bus.
[00466] [00466] The 2001 communications interface is configured to receive and send data to implement communication with another device in the communications system.
[00467] [00467] Processor 2002 is configured to implement the domain name access method provided in the embodiments shown in Figure 7 or Figures 8A, 8B and 8C. For specific details, refer to the descriptions of the previous embodiments. The details will not be described here again.
[00468] [00468] The 2003 memory is configured to store a program instruction and the like. Specifically, the program statement can include program code. The program code includes a computer operating instruction. The 2003 memory can include a RAM, or it can additionally include a non-volatile memory, for example, at least a magnetic disk memory. The processor 2002 executes the program instruction stored in memory 2003 to implement the previous function, thus implementing the domain name access method provided in the previous embodiments.
[00469] [00469] Based on the above, this application provides a domain name access method and device. In the solution, a DNS server performs the resolution on a domain name requested by a terminal device, and then sends the usage condition information and an IP address of an application server to the terminal device corresponding to the domain name obtained. through resolution. The condition of use information indicates a condition that must be met when the terminal device can access the domain name using the application server's IP address. In this way, the terminal device can perform, based on the IP address received from the application server, data transmission with the application server, and when the terminal device information is changed due to the movement of the terminal device, and the terminal device no longer meets the condition indicated by the condition of use information, the terminal device may re-execute DNS resolution on the domain name. When the terminal device information is changed and the terminal device no longer satisfies the condition indicated by the usage condition information, the application server previously obtained through the resolution can no longer be the application server that is the most suitable for the device terminal. In this case, according to the solution, the terminal device can obtain another suitable application server by re-executing the DNS resolution on the domain name. Therefore, in the solution, the communication efficiency of the terminal device can be improved, and the waste of transmission resources in a communications system is also avoided.
[00470] [00470] One skilled in the art will understand that the embodiments of this application can be provided as a method, a system or a computer program product. Therefore, this order may use a form of hardware-only embodiments, software-only embodiments, or embodiments with a combination of software and hardware. In addition, this order may use a form of a computer program product that is implemented in one or more computer-usable media
[00471] [00471] This order is described with reference to the flowcharts and / or block diagrams of the method, the device (system), and the computer program product according to this order. It will be understood that computer program instructions can be used to implement each procedure and / or each block in flowcharts and / or block diagrams and a combination of a procedure and / or a block in flowcharts and / or block diagrams. These computer program instructions can be provided for a general purpose computer, a dedicated computer, an embedded processor, or a processor from another programmable data processing device to generate a machine, so that instructions executed by a computer or a processor from another programmable data processing device generates an apparatus to implement a specific function in one or more procedures in flowcharts and / or in one or more blocks in block diagrams.
[00472] [00472] These computer program instructions can alternatively be stored in a computer-readable memory that can instruct the computer or other programmable data processing device to work in a specific way, so that the instructions stored in the computer-readable memory generate an artifact that includes an instructional apparatus. The instruction apparatus implements a specific function in one or more procedures in the flowcharts and / or in one or more blocks in the block diagrams.
[00473] [00473] These computer program instructions can alternatively be loaded onto a computer or other programmable data processing device, so that a series of operations and steps are performed on the computer or on another programmable device, thus generating processing computer-implemented. For this reason, the instructions executed on the computer or on another programmable device provide steps to implement a specific function in one or more procedures in the flowcharts and / or in one or more blocks in the block diagrams.
[00474] [00474] Obviously, one skilled in the art can make several changes and variations to this order without departing from the spirit and scope of this order. Thus, this order is intended to cover these modifications and variations of this order, as long as they are within the scope of protection defined by the claims of this order and its equivalent technologies.

权利要求:
Claims (18)
[1]
1. Domain name access method, characterized by the fact that it comprises: receiving (S301), through a DNS domain name system server, a request message from a terminal device, where the request message comprises a domain name requested by the terminal device; execute (S302), through the DNS server, the resolution in the domain name, to obtain an Internet Protocol IP address from an application server corresponding to the domain name; and send (S303), through the DNS server, a reply message to the terminal device, where the reply message comprises the IP address of the application server and usage condition information, the usage condition information indicating a condition where the terminal device accesses the domain name using the application server's IP address.
[2]
2. Method, according to claim 1, characterized in that the condition of use information comprises at least one information among the defined information and the location range information, the defined information indicating at least one IP address of the terminal device , and the location range information indicating a location range in which the terminal device is located.
[3]
3. Method, according to claim 1 or 2, characterized by the fact that it still comprises: determining, through the DNS server, the condition of use information based on the request message.
[4]
4. Method, according to claim 3, characterized in that the request message still comprises one of the location information of the terminal device and an IP address of the terminal device; and determining, through the DNS server, the condition of use information based on the request message understand: determining, through the DNS server, the condition of use information based on one of the location information of the terminal device and the IP address of the terminal device comprised in the request message.
[5]
5. Method according to any one of claims 1 to 4, characterized in that the method still comprises: sending, through the DNS server, the indication information to the terminal device, where the indication information is used to instruct the terminal device performing DNS resolution on the domain name when the terminal device does not satisfy the condition indicated by the condition of use information.
[6]
6. Domain name access method, characterized by the fact that it comprises: sending (S301), via a terminal device, a request message to a DNS domain name system server, where the request message comprises a domain name requested by the terminal device; receive (S303), through the terminal device, a reply message from the DNS server, where the reply message comprises an Internet Protocol IP address of an application server and condition of use information, the application server corresponding to the name domain, and the usage condition information indicating a condition in which the terminal device accesses the domain name using the application server's IP address; and execute (S304), through the terminal device, the DNS resolution in the domain name when the terminal device does not satisfy the condition indicated by the condition of use information.
[7]
7. Method, according to claim 6, characterized by the fact that the method still comprises: receiving, through the terminal device, the indication information from the DNS server, where the indication information is used to instruct the terminal device to execute DNS resolution on the domain name when the terminal device does not satisfy the condition indicated by the condition of use information; and determining, by means of the terminal device based on the indication information, whether the terminal device satisfies the condition indicated by the condition of use information.
[8]
8. Method, according to claim 6 or 7, characterized by the fact that the condition of use information comprises at least one information among the defined information and the location range information, the defined information indicating at least one IP address of the terminal device, and the location range information indicating a location range in which the terminal device is located; when the condition of use information comprises the defined information, that the terminal device does not satisfy the condition indicated by the condition of use information comprises: an IP address of the terminal device is changed and the changed IP address of the terminal device is not understood in at least at least one IP address indicated by the defined information; when the condition of use information comprises the location range information, that the terminal device does not satisfy the condition indicated by the condition of use information comprises: a location of the terminal device is changed and the changed location of the terminal device is not within the location range indicated by the location range information.
[9]
9. Method, according to any one of claims 6 to 8, characterized in that, after receiving, through the terminal device, a reply message from the DNS server, the method still comprises: temporarily store, through the terminal device, a DNS caching record, where the DNS caching record comprises the domain name, condition of use information and the IP address of the application server.
[10]
10. Method according to claim 9, characterized by the fact that the DNS caching record still comprises the TTL lifetime of the DNS caching record; and the determination, by means of the terminal device, that the terminal device does not satisfy the condition indicated by the condition of use information comprises: determining, by means of the terminal device, that the terminal device does not satisfy, within the TTL, the condition indicated by the condition of use information.
[11]
11. DNS domain name system server, characterized by the fact that it comprises: a receiving unit (901), configured to receive a request message from a terminal device, where the request message comprises a domain name requested by the device terminal; a processing unit (902), configured to perform domain name resolution, to obtain an Internet Protocol IP address from an application server corresponding to the domain name; and a sending unit (903), configured to send a reply message to the terminal device, where the reply message comprises the IP address of the application server and the usage condition information, the usage condition information indicating a condition in which the terminal device accesses the domain name using the application server's IP address.
[12]
12. DNS server, according to claim 11, characterized by the fact that the condition of use information comprises at least one information among the defined information and the location range information, the defined information indicating at least one IP address of the device terminal, and the location range information indicating a location range in which the terminal device is located.
[13]
13. DNS server, according to claim 11 or 12, characterized by the fact that the processing unit is still configured to: determine the condition of use information based on the request message.
[14]
14. DNS server, according to claim 13, characterized by the fact that the request message still comprises one of the terminal device's location information and an IP address of the terminal device; and when determining the condition of use information based on the request message, the processing unit must be specifically configured to: determine the condition of use information based on one of the location information of the terminal device and the IP address of the terminal device included in the request message.
[15]
15. Terminal device, characterized by the fact that it comprises: a sending unit (1001), configured to send a request message to a DNS domain name system server, where the request message comprises a domain name requested by the device terminal; a receiving unit (1002), configured to receive a response message from the DNS server, where the response message comprises an Internet Protocol IP address of an application server and the condition of use information, the application server corresponding to the domain name, and the condition of use information indicating a condition in which the terminal device accesses the domain name using the application server's IP address; and a processing unit (1003), configured to perform DNS resolution on the domain name when the terminal device does not satisfy the condition indicated by the condition of use information.
[16]
16. Terminal device, according to claim 15, characterized in that the condition of use information comprises at least one information among the defined information and the location range information, the defined information indicating at least one IP address of the device terminal, and the location range information indicating a location range in which the terminal device is located; when the condition of use information comprises the defined information, that the terminal device does not satisfy the condition indicated by the condition of use information comprises: an IP address of the terminal device is changed and the changed IP address of the terminal device is not understood in at least at least one IP address indicated by the defined information;
when the condition of use information comprises the location range information, that the terminal device does not satisfy the condition indicated by the condition of use information comprises: a location of the terminal device is changed and the changed location of the terminal device is not within the location range indicated by the location range information.
[17]
17. Terminal device according to claim 15 or 16, characterized in that the processing unit is still configured to: temporarily store a DNS caching record after the receiving unit receives the response message from the DNS server, where the DNS caching record comprises the domain name, condition of use information, and the IP address of the application server.
[18]
18. Terminal device according to claim 17, characterized by the fact that the DNS caching record still comprises the TTL lifetime of the DNS caching record; and when determining that the terminal device does not satisfy the condition indicated by the condition of use information, the processing unit will be specifically configured to: determine that the terminal device does not satisfy, within the TTL, the condition indicated by the condition condition information. use.
Petition 870200070347, of 06/05/2020, p. 120/143 UDM Entity
AMF entity SMF entity PCF entity NEF 1/19
Application server
Terminal device AN device UPF entity
DNS server
Device Device Entity Entity Entity Entity AN AMF UPF entity SMF PCF UDM terminal
Petition 870200070347, of 06/05/2020, p. 121/143 S201. Session establishment request message
S202. Select an SMF entity
S203. Session management request message (session establishment request message) S204. Procedure for obtaining signature data 2/19
S205. Session authentication procedure
S206. Obtain a CCP rule
S207. Select an UPF entity and allocate an IP address to the terminal device
S208. Updated CCP rule
To To To To To To Figure 2B Figure 2B Figure 2B Figure 2B
Continuation Continuation Continuation Continuation of Figure 2A of Figure 2A of Figure 2A of Figure 2A S209. Modification procedure
Petition 870200070347, of 06/05/2020, p. 122/143 session establishmentN4
S210. Order confirmation S211. Request session management message (terminal device IP address) S212. Configure an N2 session radio resource (IP address of the terminal device (IP address of the terminal device))
S213. N2 session request confirmation 3/19
Uplink data
S214. Update session management message (N2 session management information)
S215. N4 session modification procedure
S216. Session management update confirmation
S217. Announcement of IPv6 router Downlink data
DNS Server terminal device
S301. Request message (domain name)
S302. Perform domain name resolution to obtain an IP address from an application server corresponding to the domain name
S303. Response message (application server IP address and usage condition information)
S304. When the terminal device does not meet the condition Perform the DNS resolution indicated by the condition information in the domain name in use
Device Device Device Entity Entity Entity Server Terminal Server Server AN 1 AN 2 AMF SMF UPF 1 UPF 2 DNS application 1 application 2
S401. Establishment procedure
Petition 870200070347, of 06/05/2020, p. 124/143 session PDU 1 (in which a UPF 1 entity participates)
S402. Domain name resolution request message (domain name)
S403. Perform domain name resolution to obtain an IP address from a 5/19 server
S404. Application 1 resolution response message, and domain name determine (server IP address 1 defined information from application 1 and defined information 1)
S406. Temporarily S405. Temporarily store the record to store a record caching storage 1 cached 1 Uplink data and downlink data
S407. An SMF entity again determines to select an S408 entity. UPF NAS Anchor Message
Para Para Para Para Para Para Figure 4B Figure 4B Figure 4B Figure 4B Figure 4B
Continuation Continuation Continuation Continuation Continued from Figure 4A from Figure 4A from Figure 4A from Figure 4A from Figure 4A
Petition 870200070347, of 06/05/2020, p. 125/143 S409. Procedure for establishing a PDU 2 session (in which a UPF 2 entity participates)
S410. Determine that an IP address Message request for changed name resolution of a domain (domain name) terminal device is not included in the IP addresses indicated 6/19 by the defined information S411. Perform domain name resolution to obtain an IP address from an application server 2, and determine S412 information. Domain defined name resolution reply message 2 (application server IP address 2 and defined information 2)
S414. Temporarily S413. Temporarily store the record to store a record caching storage 2 cached 2 Uplink data and downlink data
Entity Device SMF DNS S501 terminal server. Obtaining a first domain name in a procedure of establishing a first session through a terminal device.
S502. Obtaining a second domain name in a procedure of establishing a second session through the terminal device.
Information S503. When the first domain name and the second domain name include the same S504 domain name. Perform DNS resolution on the domain name
First DN Second DN Server Server Device Device Device Entity Entity Entity Entity terminal server AN 1 AN 2 AMF SMF UPF 1 UPF 2 DNS application 1 application 2
Petition 870200070347, of 06/05/2020, p. 127/143 S601. Procedure for establishing a PDU 1 session (in which a UPF 1 entity participates)
Get a first domain name
S602. Domain name resolution request message (domain name)
S603. Perform domain name resolution to get an 8/19
S604. Name resolution reply message IP address of a domain (IP address of application server 1) Application server 1
S606. Temporarily S605. Temporarily store the record to store a record caching storage 1 cached 1 Uplink data and downlink data
S607. An SMF entity again determines to select an anchor UPF entity
Para Para Para Para Para Para Figure 6B Figure 6B Figure 6B Figure 6B Figure 6B
Continuation Continuation Continuation Continuation Continued from Figure 6A from Figure 6A from Figure 6A from Figure 6A from Figure 6A
S608. NAS Message
Petition 870200070347, of 06/05/2020, p. 128/143 S609. Procedure for establishing a PDU 2 session (in which a UPF 2 entity participates)
Get a second domain name
S610. When the Referral information first domain name and second domain name include the same domain name 9/19
S611. Domain name resolution request message (domain name)
S612. Perform resolution on the domain name for S613. Domain name resolution reply message get an IP address of (application server 2 IP address) an application server 2
S615. Temporarily S614. Temporarily store the record to store a storage record to cache 2 to cache 2 Uplink data and downlink data
Entity Entity Entity Device NEF PCF DNS terminal MF
Petition 870200070347, of 06/05/2020, p. 129/143 S701. Determine that an application server's IP address corresponding to a domain name is changed
S702. Notify a PCF entity that the IP address information of the S703 application server. Information corresponding to the 10/19 domain name indication is changed
Notify the S704 device. When a terminal IP address allocated to run for a device the terminal resolution is DNS in the name of the changed domain through an S705 DNS Server. Perform DNS resolution on the domain name
Device Device Device Entity Entity Entity Server Entity Entity Terminal Server Server AN 1 AN 2 AMF SMF UPF 1 UPF 2 DNS PCF NEF application 1 application 2
Petition 870200070347, of 06/05/2020, p. 130/143 S801. Procedure for establishing a PDU 1 session (in which a UPF 1 entity participates)
S802. Domain name request message (domain name)
S803. Perform domain name resolution for 11/19 to obtain an IP address from an S804 server. Domain name application 1 resolution response message (application server 1 IP address)
S806. S805. Temporarily temporarily store or store a storage record record cache 1 Uplink data and downlink data cached 1
To To To To To To To To To Figure 8B Figure 8B Figure 8B Figure 8B Figure 8B Figure 8B
Continuation Continuation Continuation Continuation Continuation Continued from Figure 8A from Figure 8A from Figure 8A from Figure 8A from Figure 8A from Figure 8A
S807. Function traffic targeting request message
Petition 870200070347, of 06/05/2020, p. 131/143 application
S808. Application role traffic response message
S809. Determine that the IP address information of an S810 server. Notification of application control update of session management policy corresponding (referral information) 12/19 to the domain name is changed S811. User plan reset procedure (select a UPF 2 entity) for IP address information Change notification message
S812. Allocate an IP address 2 to the S814 device. S813 resolution indication terminal information. Target DNAI of a session
Para Para Para Para Para Para Para Figure 8C Figure 8C Figure 8C Figure 8C Figure 8C Figure 8C
Continuation Continuation Continuation Continuation Continuation Continuation of Figure 8B of Figure 8B of Figure 8B of Figure 8B of Figure 8B of Figure 8B
Petition 870200070347, of 06/05/2020, p. 132/143 S815. Domain name resolution request message (domain name)
S816. S612. Perform resolution on the domain name to obtain an S817 IP address. Replies message an application domain name resolution server 2 13/19
(application server IP address 2)
S819. S818. Temporarily temporarily store the record store a cache storage record 2 cached 2 Uplink data and downlink data
DNS server
Unit Unit Unit of receiving processing processing
Terminal device
Unit Unit Unit of sending processing receiving
SMF entity
Unit Unit Unit for obtaining processing shipping
NEF entity
Unit Processing unit shipping
PCF Entity
Unit Receiving unit sending
SMF entity
Unit Receiving processing unit
DNS server
Communications Processor Interface
Memory
Terminal device
Transceiver Processor
Memory
SMF entity
Communications Processor Interface
Memory
NEF entity
Communications Processor Interface
Memory
PCF Entity
Communications Processor Interface
Memory
PCF Entity
Communications Processor Interface
Memory

类似技术:

---

公开号 | 公开日 | 专利标题

---

BR112020008132A2|2020-11-03|domain name access method and device

---

BR112020016723A2|2020-12-15|SYSTEM AND METHOD FOR EU CONTEXT AND PDU SESSION CONTEXT MANAGEMENT

---

EP3641363A1|2020-04-22|Method for inserting smf and amf entity

---

BRPI0916354B1|2020-12-08|active agent node and method

---

KR20050050518A|2005-05-31|Access router based mobile ipv6 fast handover method

---

WO2019076199A1|2019-04-25|Method, apparatus and system for determining pcf

---

BR112019011226A2|2019-10-15|load reallocation method, apparatus, and system

---

US9942909B2|2018-04-10|System and method for connection rehoming

---

US10097460B2|2018-10-09|Routing in an communications network having a distributed S/PGW architecture

---

US10945180B2|2021-03-09|Mobility management method, apparatus, and system

---

EP3614707A1|2020-02-26|State switching method and apparatus

---

WO2019134648A1|2019-07-11|Implementation method and device for control plane resource migration, and network function entity

---

US11172435B2|2021-11-09|Network entity, user equipment and method for the control and use of network slices

---

BR112020006069A2|2020-10-06|communication method, device, and system

---

JP5947982B2|2016-07-06|Serving gateway, mobility management node, method and system for obtaining data gateway

---

BR112020010523A2|2020-11-10|method, apparatus, and session processing system

---

BR112020019109A2|2020-12-29|COMMUNICATION METHOD, APPLIANCE, STORAGE MEDIA AND SYSTEM

---

JP2019176295A|2019-10-10|Gateway device, method, program, and recording medium

---

US20140133460A1|2014-05-15|Handover Method and Device

---

US11082893B2|2021-08-03|Session migration method and device applied to a UE tracking area update

---

US20210203715A1|2021-07-01|Method and apparatus for transferring an edge computing application

---

Kondo et al.2018|Development and evaluation of the MEC platform supporting the edge instance mobility

---

BR112021002797A2|2021-05-04|communication methods and apparatus, computer storage medium, chip system, communication system

---

BR112020020034A2|2021-01-05|COMMUNICATION METHOD, COMMUNICATIONS DEVICE, LEGIBLE STORAGE MEDIA, COMPUTER PROGRAM PRODUCT, AND COMMUNICATIONS SYSTEM

---

WO2021227579A1|2021-11-18|Communication system, server, and communication method and apparatus

同族专利:

---

公开号 | 公开日

---

US20210344641A1|2021-11-04|

---

EP3694187A1|2020-08-12|

---

WO2019080673A1|2019-05-02|

---

US11095606B2|2021-08-17|

---

CN109729181A|2019-05-07|

---

AU2018357503B2|2021-07-01|

---

US20200252367A1|2020-08-06|

---

CN109729181B|2020-07-24|

---

AU2018357503A1|2020-05-14|

---

CN111917829A|2020-11-10|

---

EP3694187A4|2020-08-12|

引用文献:

---

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

---

---

CN100502367C|2007-04-04|2009-06-17|华为技术有限公司|Method and device for saving domain name system record|

---

US7930427B2|2008-03-03|2011-04-19|Microsoft Corporation|Client-side load balancing|

---

CN101997903B|2009-08-27|2013-09-25|国际商业机器公司|Method and system for processing hypertext transfer protocol request|

---

CN102014173B|2010-11-01|2012-12-26|蓝汛网络科技（北京）有限公司|Domain name redirecting control method, module and system|

---

CN103348656B|2011-02-08|2016-08-17|瑞典爱立信有限公司|Method and system for the mobility support of cache self adaptation HTTP streaming content in cellular networks|

---

US10341288B2|2012-01-11|2019-07-02|Saguna Networks Ltd.|Methods circuits devices systems and associated computer executable code for providing conditional domain name resolution|

---

CN103856569B|2012-11-28|2018-09-11|方正宽带网络服务有限公司|A kind of method and apparatus of synchronous domain name system asset information|

---

US20140256286A1|2013-03-08|2014-09-11|Microsoft Corporation|Intelligent Protocol Selection|

---

CN104427007A|2013-08-23|2015-03-18|政务和公益机构域名注册管理中心|A domain name searching method for a DNS|

---

CN104427011B|2013-09-02|2019-03-22|中兴通讯股份有限公司|The method and domain name cache server of domain name mapping|

---

CN104754066B|2013-12-26|2018-10-09|华为技术有限公司|A kind of message processing method and message processor|

---

CN105338123B|2014-05-28|2018-10-02|国际商业机器公司|Methods, devices and systems for parsing domain name in a network|

---

CN104168340B|2014-07-24|2015-10-14|深圳市腾讯计算机系统有限公司|The method of domain name mapping, server, terminal and system|

---

CN105592175A|2014-10-24|2016-05-18|中兴通讯股份有限公司|Method and apparatus for redirection to web page|

---

KR102264992B1|2014-12-31|2021-06-15|삼성전자 주식회사|Method and Device for allocating a server in wireless communication system|

---

CN106412148A|2016-12-09|2017-02-15|中国联合网络通信集团有限公司|EPDG selecting method and device|

---

CN106888280A|2017-03-29|2017-06-23|北京奇虎科技有限公司|DNS update methods, apparatus and system|US10904947B2|2018-05-16|2021-01-26|Huawei Technologies Co., Ltd.|Message and system for application function influence on traffic routing|

---

CN112422701A|2019-08-20|2021-02-26|华为技术有限公司|Domain name system query method and communication device|

---

CN112468604A|2019-09-06|2021-03-09|华为技术有限公司|Method for determining domain name system server, method, device and system for processing request|

---

WO2021042398A1|2019-09-06|2021-03-11|Oppo广东移动通信有限公司|Communication method and apparatus, network device and terminal device|

---

WO2021051420A1|2019-09-21|2021-03-25|华为技术有限公司|Dns cache record determination method and apparatus|

---

CN112583880B|2019-09-30|2022-02-25|大唐移动通信设备有限公司|Server discovery method and related equipment|

---

WO2021062738A1|2019-09-30|2021-04-08|华为技术有限公司|Communication processing method and communication processing apparatus|

---

WO2021081712A1|2019-10-28|2021-05-06|华为技术有限公司|Dns query method and apparatus|

---

WO2021138804A1|2020-01-07|2021-07-15|Nokia Shanghai Bell Co., Ltd.|Method and apparatus for resolving domain name in case of local access to data network|

---

CN113473526A|2020-03-31|2021-10-01|华为技术有限公司|Communication method and device|

---

CN113518101A|2020-04-10|2021-10-19|华为技术有限公司|Application discovery method, device, system and computer storage medium|

---

CN113766040A|2020-06-05|2021-12-07|华为技术有限公司|Communication method, device and computer readable storage medium|

法律状态:
2021-12-07| B350| Update of information on the portal [chapter 15.35 patent gazette]|

优先权:

---

申请号 | 申请日 | 专利标题

---

CN201711025295.8A|CN109729181B|2017-10-27|2017-10-27|Domain name access method and device|

---

CN201711025295.8|2017-10-27|

---

PCT/CN2018/106499|WO2019080673A1|2017-10-27|2018-09-19|Domain name access method and device|

---